From: Avi Kivity <avi@redhat.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] branch and tag names
Date: Mon, 27 Apr 2009 09:33:34 +0300 [thread overview]
Message-ID: <49F551BE.9060907@redhat.com> (raw)
In-Reply-To: <8B2E6405-6772-474F-9B8F-DB1A1689CA2D@web.de>
Andreas Färber wrote:
>
> I don't see the point of having stable/0.10 though. Why do we need
> multiple stable? stable will be branched as v0.10.x, then after the
> last 0.10.x release, stable can be hard-reset to master and branched
> as v0.11.x when ready, and so on.
>
Repurposing branches is evil. Someone regularly pulls for stable, one
day it changes to something completely different. Curses.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-04-27 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 18:01 [Qemu-devel] branch and tag names Avi Kivity
2009-04-26 19:49 ` Anthony Liguori
2009-04-26 20:05 ` M. Warner Losh
2009-04-26 20:10 ` Andreas Färber
2009-04-26 21:02 ` M. Warner Losh
2009-04-26 22:05 ` Anthony Liguori
2009-04-27 6:33 ` Avi Kivity [this message]
2009-04-27 17:32 ` Andreas Färber
2009-04-27 6:32 ` Avi Kivity
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=49F551BE.9060907@redhat.com \
--to=avi@redhat.com \
--cc=andreas.faerber@web.de \
--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).