From: Junio C Hamano Date: Fri, 10 Feb 2012 20:18:35 GMT Subject: Re: Git documentation at kernel.org Message-ID: <7vhayyphlw.fsf@alter.siamese.dyndns.org> In-Reply-To: <20120210195736.GA5381@thunk.org> Ted Ts'o writes: > How about this as something *way* simpler? Define a way of marking > the top of a particular directory hierarchy as a tree. Then the > *only* way of updating that tree is all or nothing. That is, someone > submits a signed tarball; then after the signed tarball has its > signature checked, it gets unpacked into a dir.new, and then we rename > dir to dir.old, rename dir.new to dir, and then dir.old gets removed. > > That way there's no conflicts between directories that are managed via > the kup-servers PUT and DELETE commands, and those where they get > uploaded as a single tarball to create or replace a specific directory > hierarcy, or which can be deleted only as a entire directory hierarcy. > > What do you think? That would not work very well without changing the historical directory structure (which I think was the point of this discussion "please keep these stale links alive"). The toplevel index.html in the pub/software/scm/git/docs/ directory and its pointees were the set of docs for the latest version, and older versions were rooted at pub/software/scm/git/docs/vX.Y.Z/. Links that point at software/scm/git/docs/git-cat-file.html still need to work, and the path needs to be updatable without having to include the preformatted documentation for all the historical versions in the same tarball.