From: "M. Warner Losh" <imp@bsdimp.com>
To: andreas.faerber@web.de
Cc: avi@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] branch and tag names
Date: Sun, 26 Apr 2009 15:02:34 -0600 (MDT) [thread overview]
Message-ID: <20090426.150234.2106236745.imp@bsdimp.com> (raw)
In-Reply-To: <8B2E6405-6772-474F-9B8F-DB1A1689CA2D@web.de>
In message: <8B2E6405-6772-474F-9B8F-DB1A1689CA2D@web.de>
Andreas_Färber <andreas.faerber@web.de> writes:
:
: Am 26.04.2009 um 21:49 schrieb Anthony Liguori:
:
: > Avi Kivity wrote:
: >> Can we move to
: >>
: >> v0.10.0
: >> stable/0.10
: >
: > v0.10.0 as a tag looks good to me.
: >
: > stable/0.10 feels a little awkward. I never have gotten quite used
: > to this style of tagging (using file-like hierarchies).
: >
: > I'm not super opinionated about it either way. I'm interested to
: > see what other people think.
:
: +1 for v0.10.2
:
: 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.
It allows people to grab the historical branches if they want...
Warner
next prev parent reply other threads:[~2009-04-26 21:04 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 [this message]
2009-04-26 22:05 ` Anthony Liguori
2009-04-27 6:33 ` Avi Kivity
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=20090426.150234.2106236745.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=andreas.faerber@web.de \
--cc=avi@redhat.com \
--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.