From: Dave Hansen <haveblue@us.ibm.com>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] kpatchup 0.02 kernel patching script
Date: Thu, 04 Mar 2004 10:50:10 -0800 [thread overview]
Message-ID: <1078426209.19701.1382.camel@nighthawk> (raw)
In-Reply-To: <20040304183516.GN3883@waste.org>
On Thu, 2004-03-04 at 10:35, Matt Mackall wrote:
> I skimmed latest-kernel-version, is it doing something my -s option
> doesn't do yet?
$ ./kpatchup-0.03 -s 2.6-bk
2.6.4-rc1-bk4
$ ./kpatchup-0.03 -s 2.6
2.6.3
$ ./kpatchup-0.03 -s 2.6-pre
2.6.4-rc2
$ latest-kernel-version --probe
2.6.4-rc2
I might be misunderstanding the options, but 'kpatchup -s' I think is
limited to giving the latest version of a single tree, while
'latest-kernel-version' will look at several different trees. This is a
tiny problem for kpatchup because it treats 2.6, 2.6-bk, and 2.6-pre as
separate trees. For my use, I just want the latest snapshot, whether
it's a bk snapshot, or one of the real point releases.
What I'm doing to work around it is this:
kpatchup `latest-kernel-version --probe`
-- dave
next prev parent reply other threads:[~2004-03-04 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 2:24 [ANNOUNCE] kpatchup 0.02 kernel patching script Matt Mackall
2004-03-03 5:51 ` Zwane Mwaikambo
2004-03-04 1:40 ` Rusty Russell
2004-03-04 17:22 ` Dave Hansen
2004-03-04 18:35 ` Matt Mackall
2004-03-04 18:50 ` Dave Hansen [this message]
2004-03-04 19:09 ` Matt Mackall
2004-03-04 19:14 ` Dave Hansen
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=1078426209.19701.1382.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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