From: Spelic <spelic@shiftmail.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Can't find fourth number version tags in GIT kernel
Date: Sat, 27 Nov 2010 14:07:22 +0100 [thread overview]
Message-ID: <4CF1028A.6010401@shiftmail.org> (raw)
Hello LKML
I'm trying to use GIT to stay up-to-date with the kernel sources, but in
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
and even
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.36.y.git
I can't find versions with four numbers, e.g. I do find tag:
v2.6.35
(and also the release candidates for 2.6.35)
but I can't find tags:
v2.6.35.1
v2.6.35.2
...
v2.6.35.9
Apparently tag v2.6.35 really brings me to v2.6.35.0 and not to
v2.6.35.9 so it's a problem... I usually want to get the highest number
in the fourth number, not the lowest.
Like this I don't know how to get the bugfixes...?
What am I missing?
Thank you
PS: can you please reply to me also, as I am not subscribed to LKML. Thanks
next reply other threads:[~2010-11-27 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 13:07 Spelic [this message]
2010-11-27 13:38 ` Can't find fourth number version tags in GIT kernel Lionel Debroux
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=4CF1028A.6010401@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=linux-kernel@vger.kernel.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