From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
David Woodhouse <dwmw2@infradead.org>,
"YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.21-gitN - versioning question
Date: Sat, 12 May 2007 20:39:56 +0400 [thread overview]
Message-ID: <20070512163956.GA9048@cvg> (raw)
In-Reply-To: <20070512163141.GC21729@flint.arm.linux.org.uk>
[Russell King - Sat, May 12, 2007 at 05:31:41PM +0100]
| On Sat, May 12, 2007 at 08:24:28PM +0400, Cyrill Gorcunov wrote:
| > [Jan Engelhardt - Sat, May 12, 2007 at 05:01:19PM +0200]
| > |
| > | On May 12 2007 21:44, David Woodhouse wrote:
| > | >On Sat, 2007-05-12 at 17:19 +0400, Cyrill Gorcunov wrote:
| > | >> Actually I think it would be convenient if such tags (like
| > | >> v.2.6.21-git16) were in Linus' git tree too.
| > | >
| > | >Then there would be _lots_ of tags in the master tree -- I'm not sure we
| > | >want that.
| > | >
| > | >I suppose I could put a tree on kernel.org which _does_ have the tags,
| > | >and which precisely matches Linus' tree in every other way... but then
| > | >again, you could do that too by just rsyncing the tags yourself :)
| > |
| > | Are you saying GIT tags are expensive, compared to, say, SVN tags?
|
| (Sorry, don't have Jan's message.)
|
| The real issue is not that, but that David doesn't have write access to
| Linus' published tree. Neither should he because he could contaminate
| Linus' published tree with the MTD tree, or introduce some unreviewed
| patch which gave him backdoor access via the kernel.
|
| (Of course, David's unlikely to do either, but that's not really the
| point.)
|
| --
| Russell King
| Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
| maintainer of:
|
The only reason I wrote some messages to this theme is that on
my point of view the using of tags like "v2.6.21-git16" would be
convenient. But that should be Linus' decision (thanks to David
for proposed solution). Anyway if Linus doesn't want to keep
a such tags in hisown tree I prefer to do the same ;)
Cyrill
next prev parent reply other threads:[~2007-05-12 16:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 11:19 linux-2.6.21-gitN - versioning question Jan Engelhardt
2007-05-12 11:31 ` Adrian Bunk
2007-05-12 12:03 ` YOSHIFUJI Hideaki / 吉藤英明
2007-05-12 13:19 ` Cyrill Gorcunov
2007-05-12 13:44 ` David Woodhouse
2007-05-12 14:01 ` Cyrill Gorcunov
2007-05-12 15:01 ` Jan Engelhardt
2007-05-12 15:58 ` Cyrill Gorcunov
2007-05-12 16:24 ` Cyrill Gorcunov
2007-05-12 16:31 ` Russell King
2007-05-12 16:39 ` Cyrill Gorcunov [this message]
2007-05-13 6:26 ` David Woodhouse
2007-05-13 6:43 ` Cyrill Gorcunov
2007-05-13 6:50 ` David Woodhouse
2007-05-13 7:13 ` Cyrill Gorcunov
2007-05-12 18:17 ` H. Peter Anvin
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=20070512163956.GA9048@cvg \
--to=gorcunov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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