From: Paul Bolle <pebolle@tiscali.nl>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net
Subject: Re: Linux 3.0.8
Date: Thu, 27 Oct 2011 14:02:49 +0200 [thread overview]
Message-ID: <1319716969.20488.14.camel@x61.thuisdomein> (raw)
In-Reply-To: <20111025051928.GA7997@kroah.com>
On Tue, 2011-10-25 at 07:19 +0200, Greg KH wrote:
> The updated 3.0.y git tree can be found at (NOTE THE ADDRESS CHANGE):
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.0.y
> and can be browsed at the normal kernel.org git web browser:
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
Somehow I seem to be able to generate perfect copies of patch-3.0.4.bz2
(and earlier), by simply doing a command like:
git diff v3.0 v3.04 | bzip2 -9 > patch-3.0.4-git.bz2
But for patch-3.0.5 (and above) trivial commands like
git diff v3.0 v3.0.8 > patch-3.0.8-git
do not generate perfect copies anymore. Have you perhaps changed the way
you generate the patches since v3.0.5? Not that this matters much,
since tags v3.0.5 (and up) are signed by your "Linux kernel stable
release signing key", but I still wonder what could cause this
difference. Maybe it's just a git upgrade on your side.
Paul Bolle
next prev parent reply other threads:[~2011-10-27 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 5:19 Greg KH
2011-10-25 5:20 ` Greg KH
2011-10-25 5:40 ` Randy Dunlap
2011-10-25 7:02 ` Greg KH
2011-10-25 8:41 ` Valdis.Kletnieks
2011-10-26 8:14 ` Mike Galbraith
2011-10-26 16:39 ` Randy Dunlap
2011-10-27 12:02 ` Paul Bolle [this message]
2011-10-27 12:08 ` Greg KH
2011-10-27 12:57 ` Paul Bolle
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=1319716969.20488.14.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®