Messages in this thread | | | Date | Thu, 4 Mar 2004 13:09:27 -0600 | From | Matt Mackall <> | Subject | Re: [ANNOUNCE] kpatchup 0.02 kernel patching script |
| |
On Thu, Mar 04, 2004 at 10:50:10AM -0800, Dave Hansen wrote: > 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
This is actually broken at the moment as it won't know how to fetch stuff from old/ when it's given a non-current bk version. I have a design assumption that I can go from a version name to a URL without any lookups, which the snapshot dir purging breaks.
ISTR Jeff maintains the snapshot scripts. Jeff, could you possibly have it put a copy of the each snapshot in old/ at creation time rather than moving stuff there at a later point? This will make URLs pointing to old/ for -bk patches stable but shouldn't break anything else.
> $ ./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.
I suppose I could add a 2.6-tip, which will return the greatest of 2.6, 2.6-pre, and 2.6-bk. Like this:
$ kpatchup -s 2.6-tip 2.6.4-rc2 $ kpatchup -u 2.6-tip http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.4-rc2.bz2
-- Matt Mackall : http://www.selenic.com : Linux development and consulting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |