From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: maintenance releases in GIT tree
Date: Wed, 25 Jan 2006 21:10:40 -0800 [thread overview]
Message-ID: <20060126051040.GA12289@kroah.com> (raw)
In-Reply-To: <20060126035533.GA22994@quickstop.soohrt.org>
On Thu, Jan 26, 2006 at 04:55:33AM +0100, Horst Schirmeier wrote:
> Hi,
>
> why are the maintenance releases (2.6.x.y -- those with a .y in their
> version number) not stored in the git tree accessible via
> rsync://rsync1.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/?
> (Or -- are they, and I'm just not seeing them because I'm looking at the
> wrong corner in the .git/ subdirectory?)
They are not released by Linus, so why would they be in his tree? :)
As per the release announcements, they are located in either:
pub/scm/linux/kernel/git/gregkh/linux-2.6.15.y.git
or
pub/scm/linux/kernel/git/chrisw/linux-2.6.15.y.git
depending on who did the release. Check the lkml message for specifics
on which it is.
Hope this helps,
greg k-h
prev parent reply other threads:[~2006-01-26 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 3:55 maintenance releases in GIT tree Horst Schirmeier
2006-01-26 5:10 ` Greg KH [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=20060126051040.GA12289@kroah.com \
--to=greg@kroah.com \
--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