From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.9.1
Date: Wed, 8 May 2013 11:28:37 -0700 [thread overview]
Message-ID: <20130508182837.GA26128@kroah.com> (raw)
In-Reply-To: <20130508181943.GC4169@fysh.org>
On Wed, May 08, 2013 at 07:19:43PM +0100, Athanasius wrote:
> On Wed, May 08, 2013 at 10:50:20AM -0700, Greg KH wrote:
> > On Wed, May 08, 2013 at 08:22:45AM +0100, Athanasius wrote:
> > > On Tue, May 07, 2013 at 09:10:10PM -0700, Greg KH wrote:
> > > > I'm announcing the release of the 3.9.1 kernel.
> > > >
> > > > All users of the 3.9 kernel series must upgrade.
> > > >
> > > > The updated 3.9.y git tree can be found at:
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.9.y
> > >
> > > Usually I can:
> > >
> > > git pull git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git master
> >
> > If you do that, you only get the master branch updated locally. Which
> > tracks Linus's tree, not the different stable releases.
> >
> > > which means not having to update scripts/commandline history on each
> > > major verison change, but this time I did indeed need to:
> > >
> > > git pull git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.9.y
> > >
> > > is this an intended change, or did you do something like forgetting to
> > > merge into master on linux-stable ?
> >
> > No, I have not changed anything on my end, perhaps you never really were
> > updating the different stable branches?
>
> 'uname -r' says I was. Also 'git log' for my v3.8 branch currently on
> 3.8.9 via the 'master' method does include at least the top few commits
> listed on:
>
> <https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.8.9>
>
> Of course only having gotten to 3.8.9 a pull against linux-3.8.y does
> see changes. Perhaps someone else, or a script on git.kernel.org was
> merging into master before and now isn't ?
No, nothing was ever mergeing into master in the linux-stable git tree.
You might have been doing that locally, check the merges to see who was
doing it.
> Anyway, if it's unsupported to pull from linux-stable.git master I'll
> change my scripts.
It's not unsupported, you will just get a copy of Linus's tree there,
delayed by usually a -rc release or so.
thanks,
greg k-h
next prev parent reply other threads:[~2013-05-08 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 4:10 Linux 3.9.1 Greg KH
2013-05-08 4:10 ` Greg KH
2013-05-08 7:22 ` Athanasius
2013-05-08 17:50 ` Greg KH
2013-05-08 18:19 ` Athanasius
2013-05-08 18:28 ` Greg KH [this message]
2013-05-08 18:48 ` Athanasius
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=20130508182837.GA26128@kroah.com \
--to=gregkh@linuxfoundation.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