From: Junio C Hamano <gitster@pobox.com>
To: Clemens Buchacher <drizzd@aon.at>
Cc: ftpadmin@kernel.org, Petr Onderka <gsvick@gmail.com>,
git@vger.kernel.org
Subject: Re: Git documentation at kernel.org
Date: Thu, 09 Feb 2012 16:23:01 -0800 [thread overview]
Message-ID: <7vmx8rtu3e.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120208213410.GA5768@ecki> (Clemens Buchacher's message of "Wed, 8 Feb 2012 22:34:10 +0100")
Clemens Buchacher <drizzd@aon.at> writes:
> Please restore access to the following files when possible. Some sites
> are referencing those, including kernel.org itself:
>
> http://www.kernel.org/pub/software/scm/git/docs/git.html
The pages reachable from this used to be living documents in that every
time the 'master' branch was updated at k.org, automatically a server side
hook script generated a new set of HTML pages and updated them.
My understanding is that we do not want to run such random server side
hooks at k.org, so it no longer can be a living document anymore.
It might be a workable short term workaround to redirect
http://www.kernel.org/pub/software/scm/git/docs/$anything
to
http://schacon.github.com/git/$anything
although that would not give you an access to the list of documentations
for older releases, e.g.
http://www.kernel.org/pub/software/scm/git/docs/v1.6.0/git.html
> Also, it would be great if the git wiki could be made editable again.
Amen.
next prev parent reply other threads:[~2012-02-10 0:23 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 [this message]
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
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=7vmx8rtu3e.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=drizzd@aon.at \
--cc=ftpadmin@kernel.org \
--cc=git@vger.kernel.org \
--cc=gsvick@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).