From: Ted Ts'o <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Konstantin Ryabitsev <icon@mricon.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Clemens Buchacher <drizzd@aon.at>,
ftpadmin@kernel.org, Petr Onderka <gsvick@gmail.com>,
git@vger.kernel.org
Subject: Re: Git documentation at kernel.org
Date: Fri, 10 Feb 2012 16:20:30 -0500 [thread overview]
Message-ID: <20120210212030.GD5381@thunk.org> (raw)
In-Reply-To: <7vhayyphlw.fsf@alter.siamese.dyndns.org>
On Fri, Feb 10, 2012 at 12:18:35PM -0800, Junio C Hamano wrote:
> 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.
Hmm... good point. That does make it hard. I could imagine making it
work by having separate hierarchies, and then using apache rewrite
rules so that anything that doesn't begin with vX.Y.Z in the top level
of software/scm/git/docs/* gets redirected to LATEST/*, where LATEST is
a symlink that is managed via kup.
I don't know if the k.org folks would consider that acceptable, though.
- Ted
next prev parent reply other threads:[~2012-02-10 21:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 12:28 Git documentation at kernel.org Petr Onderka
2012-02-08 21:34 ` Clemens Buchacher
2012-02-10 0:23 ` Junio C Hamano
2012-02-10 16:59 ` Matthieu Moy
2012-02-10 18:00 ` Theodore Tso
2012-02-10 18:55 ` Konstantin Ryabitsev
2012-02-10 19:57 ` Ted Ts'o
2012-02-10 20:18 ` Junio C Hamano
2012-02-10 21:20 ` Ted Ts'o [this message]
2012-02-10 21:38 ` Junio C Hamano
2012-02-10 20:01 ` Jeff King
2012-02-10 19:51 ` Junio C Hamano
2012-02-10 20:04 ` Jeff King
2012-02-12 22:04 ` Matthieu Moy
2012-02-12 22:25 ` Jeff King
2012-02-12 23:04 ` Scott Chacon
2012-02-13 0:30 ` Jeff King
2012-02-13 3:23 ` Junio C Hamano
2012-02-14 22:15 ` Jeff King
2012-02-13 15:15 ` Konstantin Ryabitsev
2012-02-10 1:04 ` Neal Kreitzinger
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=20120210212030.GD5381@thunk.org \
--to=tytso@mit.edu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=drizzd@aon.at \
--cc=ftpadmin@kernel.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gsvick@gmail.com \
--cc=icon@mricon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.