From: Anthony Liguori <anthony@codemonkey.ws>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "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 07:07:33 -0600 [thread overview]
Message-ID: <4D4FEE95.3050603@codemonkey.ws> (raw)
In-Reply-To: <4D4D1434.6060209@msgid.tls.msk.ru>
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.
Regards,
Anthony Liguori
> /mjt
>
>
next prev parent reply other threads:[~2011-02-07 13:08 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 [this message]
2011-02-07 14:09 ` Markus Armbruster
2011-02-07 14:32 ` Anthony Liguori
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=4D4FEE95.3050603@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.