public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Live source based ebuild proposals
Date: Sat, 14 Feb 2009 00:46:54 +0100	[thread overview]
Message-ID: <4996066E.90306@gentoo.org> (raw)
In-Reply-To: <20090213225209.7ef5403e@snowmobile>

Ciaran McCreesh wrote:
> On Fri, 13 Feb 2009 23:35:34 +0100
> Luca Barbato <lu_zero@gentoo.org> wrote:
>>> Hence -scm...
>> that cannot do as well for more than a single target w/out using use
>> flags.
> 
> Because it isn't supposed to. Versions and topics are not the same
> thing, and treating topics as versions leads to mishandling.
> 

master is just a name, you may have the main development happen in 
another branch (say devel) and the stabler tree is kept on the master 
branch and you may want to track both as well.

Or even worse, you get two lines of development you want to track that 
stay in completely different vcs. And that is the case of a real 
package, not theory. In those cases having a template could help a bit, 
having -scm + useflag is exactly the same as having bare useflags and slots.

>> Then if you continued to read you'll notice that
> 
> ...you got so incoherent I gave up trying to work out what you're on
> about. You still haven't shown how to solve the simple example I gave
> earlier in the thread.

Relying to offense because I just pointed out something you dislikes 
since you cannot find a argumentative way reply isn't exactly polite or 
mature.


-- 

Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero




  reply	other threads:[~2009-02-13 23:47 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 [this message]
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

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=4996066E.90306@gentoo.org \
    --to=lu_zero@gentoo.org \
    --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