From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Scott Chacon <schacon@gmail.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: Tue, 14 Feb 2012 17:15:25 -0500 [thread overview]
Message-ID: <20120214221525.GD24802@sigill.intra.peff.net> (raw)
In-Reply-To: <7vmx8nju1k.fsf@alter.siamese.dyndns.org>
On Sun, Feb 12, 2012 at 07:23:19PM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > That sounds great to me. I'd like to be link-compatible with the old
> > kernel.org docs section (even if through redirects) so that old links
> > work (assuming kernel.org gives us a wholesale redirect). Which means
> > importing all of the docs for released versions. I don't know if the old
> > kernel.org doc tree was saved anywhere, but if I understand correctly,
> > they are identical to what's in the "git-htmldocs" repository (which I
> > _thought_ Junio wasn't going to keep updating, but it seems pretty up to
> > date).
> [...]
> But the contents of htmldocs does _not_ match what used to be at k.org in
> that its git.html does not have links to documentation pages for older
> releases, iow, formatted without "stalenotes" defined.
Ah, that makes sense. We might have to just rebuild the old versions
with stalenotes, then (our doc toolchain is so finicky that I worry
about minor incompatibilities in building old versions with a newer
toolchain, but it is probably good enough).
-Peff
next prev parent reply other threads:[~2012-02-14 22:15 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
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 [this message]
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=20120214221525.GD24802@sigill.intra.peff.net \
--to=peff@peff.net \
--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=schacon@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).