From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] branch and tag names
Date: Mon, 27 Apr 2009 09:32:32 +0300 [thread overview]
Message-ID: <49F55180.7010105@redhat.com> (raw)
In-Reply-To: <49F4BAB7.3010501@codemonkey.ws>
Anthony Liguori wrote:
>
> stable/0.10 feels a little awkward. I never have gotten quite used to
> this style of tagging (using file-like hierarchies).
It's useful if you have multiple categories of branches (personal
development branches, formal maintenance branches, semi-formal branches
for early sharing). Probably not so important for the master repository.
>
> I'm not super opinionated about it either way.
Pity, it's even better bikeshedding material than directory layouts.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-04-27 6:32 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
2009-04-27 17:32 ` Andreas Färber
2009-04-27 6:32 ` Avi Kivity [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=49F55180.7010105@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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).