public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Live source based ebuild proposals
Date: Sat, 14 Feb 2009 02:38:33 +0000 (UTC)	[thread overview]
Message-ID: <pan.2009.02.14.02.38.32@cox.net> (raw)
In-Reply-To: 20090213222233.40efa9fd@snowmobile

Ciaran McCreesh <ciaran.mccreesh@googlemail.com> posted
20090213222233.40efa9fd@snowmobile, excerpted below, on  Fri, 13 Feb 2009
22:22:33 +0000:

>> > How do I track an upstream who has a 0.34 branch (which is equal to
>> > or ahead of the most recent 0.34.x release)  a 0.36 branch (which is
>> > equal to or ahead of the most recent 0.36.x release)
>> 
>> In those cases is enough take the package version and add one w/out
>> requiring any additional version component...
> 
> Be specific. Explain how this works when, say, 0.34.4 is current, you
> have a 0.34.5_live and 0.34.5 comes out.

Luca, I didn't follow this bit either.  The way I read your "add one" 
Ciaran's example went off the mark, but then my read didn't work too well 
either, so if you could fill in the concrete numbers you had in mind, it 
will hopefully clarify things. (Add one /where/, to which segment of the 
version?)

Being as concrete in the examples as possible helps.  It might seem to go 
on needlessly, but when the alternative is not being sure what you were 
talking about and thus possibly going off on a tangent...  To Ciaran's 
credit, he's at least using concrete version numbers/strings in his 
examples, so there's no mistaking what he had in mind.  Unfortunately, 
without this concreteness I think it's just going to be yet another 
argument in a circle, and I think/hope everybody's agreed there have been 
enough of those on this subject already.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




      parent reply	other threads:[~2009-02-14  2:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090212214925.GA21532@dodo.hsd1.nj.comcast.net>
     [not found] ` <20090213155445.GA31550@dodo.hsd1.nj.comcast.net>
     [not found]   ` <4995ABE2.4000907@gentoo.org>
     [not found]     ` <20090213172725.34258824@snowcone>
     [not found]       ` <4995CB0B.80209@gentoo.org>
     [not found]         ` <20090213194141.24d44a37@snowcone>
2009-02-13 20:29           ` [gentoo-dev] Live source based ebuild proposals Was: [gentoo-council] Council log and summary for meeting on 02/12/09 Luca Barbato
2009-02-13 20:37             ` [gentoo-dev] " Ciaran McCreesh
2009-02-13 22:17               ` [gentoo-dev] Re: Live source based ebuild proposals Luca Barbato
2009-02-13 22:22                 ` Ciaran McCreesh
2009-02-13 22:35                   ` Luca Barbato
2009-02-13 22:52                     ` Ciaran McCreesh
2009-02-13 23:46                       ` Luca Barbato
2009-02-13 23:53                         ` Ciaran McCreesh
2009-02-14  1:19                           ` Ryan Hill
2009-02-14  2:57                             ` Duncan
2009-02-14 13:46                             ` Luca Barbato
2009-02-14  2:28                           ` Duncan
2009-02-14 14:41                           ` Luca Barbato
2009-02-15  8:05                             ` Duncan
2009-02-15 10:55                             ` Luca Barbato
2009-02-14  2:38                   ` Duncan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2009.02.14.02.38.32@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox