From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] branch and tag names
Date: Sun, 26 Apr 2009 14:49:11 -0500 [thread overview]
Message-ID: <49F4BAB7.3010501@codemonkey.ws> (raw)
In-Reply-To: <49F4A162.4000604@redhat.com>
Avi Kivity wrote:
> Currently, tags and branch names carry their cvs heritage:
>
> release_0_10_0
> stable_0_10
And I even renamed them to make them less unslightly :-) They were
something like svn/tags/release_0_10_0.
> These are unsightly. 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.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-26 19:49 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 [this message]
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
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=49F4BAB7.3010501@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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.