From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: jengelh@linux01.gwdg.de, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.21-gitN - versioning question
Date: Sat, 12 May 2007 17:19:06 +0400 [thread overview]
Message-ID: <20070512131906.GF8337@cvg> (raw)
In-Reply-To: <20070512.210308.93070730.yoshfuji@linux-ipv6.org>
[YOSHIFUJI Hideaki / ?$B5HF#1QL@ - Sat, May 12, 2007 at 09:03:08PM +0900]
| In article <Pine.LNX.4.61.0705121316540.9570@yvahk01.tjqt.qr> (at Sat, 12 May 2007 13:19:23 +0200 (MEST)), Jan Engelhardt <jengelh@linux01.gwdg.de> says:
|
| > I notice that people refer to certain git snapshots as e.g. -git16;
| > kernel.org does so too. Hovering over the link on kernel.org reveals
| > http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.21-git16.bz2
| > but where do I actually find -git16 in Linus's git tree? git16 is
| > neither a branch nor a tag.
|
| http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.21-git16.id
| tells the commit in his tree.
|
| --yoshfuji
Actually I think it would be convenient if such tags (like v.2.6.21-git16)
were in Linus' git tree too.
Cyrill
next prev parent reply other threads:[~2007-05-12 13:19 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 [this message]
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
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=20070512131906.GF8337@cvg \
--to=gorcunov@gmail.com \
--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