From: Athanasius <link@miggy.org>
To: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.9.1
Date: Wed, 8 May 2013 19:48:36 +0100 [thread overview]
Message-ID: <20130508184836.GD4169@fysh.org> (raw)
In-Reply-To: <20130508182837.GA26128@kroah.com>
On Wed, May 08, 2013 at 11:28:37AM -0700, Greg KH wrote:
> On Wed, May 08, 2013 at 07:19:43PM +0100, Athanasius wrote:
> > '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.
It really is just your Makefile/version commits, and then the commits
you merged in to make the release.
> > 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.
I'm going to guess that what happened then was I was lucky enough for
Linus to have released a new -rc by the time I pulled a new stable. So,
then checking out the stable tag would have pointed to the right commit
to also checkout the associated commits.
Anyway, enough noise over this now.
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
prev parent reply other threads:[~2013-05-08 18:48 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
2013-05-08 18:48 ` Athanasius [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=20130508184836.GD4169@fysh.org \
--to=link@miggy.org \
--cc=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