linux-kernel - Re: [kernel.org users] XZ Migration discussion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1266009364.24271.86.camel@gandalf.stny.rr.com>
Date:	Fri, 12 Feb 2010 16:16:04 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Junio C Hamano <gitster@...ox.com>
Cc:	Jean Delvare <khali@...ux-fr.org>, "J.H." <warthog9@...nel.org>,
	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>, users@...nel.org,
	lasse.collin@...aani.org,
	linux-kernel <linux-kernel@...r.kernel.org>, mirrors@...nel.org
Subject: Re: [kernel.org users] XZ Migration discussion

On Fri, 2010-02-12 at 12:34 -0800, Junio C Hamano wrote:
> Steven Rostedt <rostedt@...dmis.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.

Are you suggesting that the path be stored at a known location on
kernel.org? Such that it can be read and the tools like ketchup can find
where a particular version resides?

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/