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 09:22:02 -0800 [thread overview]
Message-ID: <1078420922.19701.1362.camel@nighthawk> (raw)
In-Reply-To: <20040303022444.GA3883@waste.org>
On Tue, 2004-03-02 at 18:24, Matt Mackall wrote:
> This is an alpha release for people to experiment with. Feedback and
> patches encouraged. Grab your copy today at:
First of all, very nice script.
But, it doesn't look like it properly handles empty directories. I
tried this command, this morning, and it blew up. I think it's because
this directory http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/ is
empty because of last night's 2.6.4-rc2 release. I don't grok python
very well but is the "return p[-1]" there just to cause a fault like
this? Would it be better if it just returned a "no version of that
patch right now" message and exited nicely?
[dave@nighthawk linux-2.6]$ kpatchup-0.02 2.6-bk
"Traceback (most recent call last):
File "/home/dave/bin/kpatchup-0.02", line 283, in ?
b = find_ver(args[0])
File "/home/dave/bin/kpatchup-0.02", line 240, in find_ver
return v[0](os.path.dirname(v[1]), v[2])
File "/home/dave/bin/kpatchup-0.02", line 147, in latest_dir
return p[-1]
IndexError: list index out of range
I think your script, combined with Rusty's latest-kernel-version could
make me a very happy person.
-- dave
next prev parent reply other threads:[~2004-03-04 17:23 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 [this message]
2004-03-04 18:35 ` Matt Mackall
2004-03-04 18:50 ` Dave Hansen
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=1078420922.19701.1362.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