Messages in this thread |  | | | Subject | Re: [kernel.org users] XZ Migration discussion | | From | Junio C Hamano <> | | Date | Fri, 12 Feb 2010 12:34:25 -0800 |
| |
Steven Rostedt <rostedt@goodmis.org> writes:
> On Fri, 2010-02-12 at 17:11 +0100, Jean Delvare wrote: > >> What would you consider a reasonable turnaround time? 3 month? 6 month? >> More? >> >> We could make a decision now, you update ketchup immediately, and the >> actual change happens at the specified date in the future. >> > > Usually users don't update ketchup until it breaks ;)
Then the archive location can change immediately after you issue an update ;-)
Would it be an option for a newer version of ketchup to have a fallback codepath to read a machine-readable description of how the archive is structured from a known location? E.g. instead of appending a hard-coded string '/people/akpm/patches/2.6/' when computing latest_mm(), the script would read that "relative path to mm" from such a description file. The logic of doing 'url = "%s/v%s/%s" % (kernel_url, t, f)' in install_nearest would similarly be customizable, without too much hassle, I think.
|  |