From: Jens Axboe <axboe@suse.de>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org, torvalds@osdl.org
Subject: Re: Linux 2.6.16.1
Date: Tue, 28 Mar 2006 10:08:24 +0200 [thread overview]
Message-ID: <20060328080824.GB8186@suse.de> (raw)
In-Reply-To: <20060328080114.GC8097@kroah.com>
On Tue, Mar 28 2006, Greg KH wrote:
> On Mon, Mar 27, 2006 at 11:56:29PM -0800, Greg KH wrote:
> > We (the -stable team) are announcing the release of the 2.6.16.1 kernel.
> >
> > The diffstat and short summary of the fixes are below.
> >
> > I'll also be replying to this message with a copy of the patch between
> > 2.6.16 and 2.6.16.1, as it is small enough to do so.
> >
> > The updated 2.6.16.y git tree can be found at:
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.15.y.git
>
> Oops, that should be:
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
>
> sorry about that...
>
> Hm, we shouldn't be using "rsync" as part of a git url these days.
> What's the recommended way of writing kernel.org git tree addresses now?
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
?
--
Jens Axboe
next prev parent reply other threads:[~2006-03-28 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 7:56 Linux 2.6.16.1 Greg KH
2006-03-28 7:57 ` Greg KH
2006-03-28 8:01 ` Greg KH
2006-03-28 8:08 ` Jens Axboe [this message]
2006-03-30 19:46 ` Beber
2006-03-30 22:35 ` [PATCH] isd200: limit to BLK_DEV_IDE Randy.Dunlap
2006-03-30 23:03 ` Linus Torvalds
2006-03-30 23:25 ` Randy.Dunlap
2006-03-30 23:41 ` Linus Torvalds
2006-03-31 7:52 ` Bertrand Jacquin
[not found] ` <4615f4910604050635v5af3dbc6w17849adb2fd64593@mail.gmail.com>
2006-04-05 18:45 ` [stable] " Greg KH
2006-04-05 19:04 ` Randy.Dunlap
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=20060328080824.GB8186@suse.de \
--to=axboe@suse.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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