qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	"Justin M. Forbes" <jmforbes@linuxtx.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] New stable branch information
Date: Mon, 07 Feb 2011 08:32:02 -0600	[thread overview]
Message-ID: <4D500262.9060102@codemonkey.ws> (raw)
In-Reply-To: <m3hbcgndg1.fsf@blackfin.pond.sub.org>

On 02/07/2011 08:09 AM, Markus Armbruster wrote:
> Anthony Liguori<anthony@codemonkey.ws>  writes:
>
>    
>> On 02/05/2011 03:11 AM, Michael Tokarev wrote:
>>      
>>> 04.02.2011 15:25, Anthony Liguori wrote:
>>>
>>>        
>>>> To help make the stable branch more active than it has been in the past,
>>>> I'd like to split the stable branch into a separate tree to allow the
>>>> tree to develop a life of its own over time.
>>>>
>>>>          
>>> What's the difference between a separate tree and a branch in main tree?
>>> Why separate tree is needed?  As far as I can see, both serves the same
>>> purpose, but to me a separate branch is easier to handle (comparing etc).
>>>
>>>        
>> Without overhauling how we host our git tree, I can't give fine grain
>> access to specific branches.
>>
>> I'm going to look into that in the not too distant future but it's not
>> going to happen short term.
>>
>> So for now, we'll have separate trees and I'll work on getting the
>> right infrastructure such that we can have one.
>>      
> You go ahead do what you think is right, but I wouldn't bother with
> this.  Separate trees are easier to set up and maintain, and they're
> almost as easy to use: just pull from all the trees you're interested.
>    

Yeah, for folks that aren't familiar with remotes, it's worth reading 
http://gitref.org/remotes/#remote

I have probably a couple dozen remotes in my qemu tree.  Once it's 
setup, there's really no difference in working with a branch in a 
different tree than working with one on origin.

But I still like the idea of a single tree.

Regards,

Anthony Liguori

      reply	other threads:[~2011-02-07 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 12:25 [Qemu-devel] New stable branch information Anthony Liguori
2011-02-04 19:26 ` Aurelien Jarno
2011-02-04 20:48   ` Justin M. Forbes
2011-02-05  9:11 ` Michael Tokarev
2011-02-07 13:07   ` Anthony Liguori
2011-02-07 14:09     ` Markus Armbruster
2011-02-07 14:32       ` Anthony Liguori [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=4D500262.9060102@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=jmforbes@linuxtx.org \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).