From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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 17:59:25 +0100 [thread overview]
Message-ID: <vpqbop6tyj6.fsf@bauges.imag.fr> (raw)
In-Reply-To: <7vmx8rtu3e.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 09 Feb 2012 16:23:01 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> 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.
Is it possible to have the static HTML uploaded from another machine,
not necessarily for each push, but e.g. for every release?
I don't think anyone cares about having the very latest documentation
there, but it would still be great to have an official place to point to
when writing documentation on the web about such or such command.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-02-10 17:01 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 [this message]
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=vpqbop6tyj6.fsf@bauges.imag.fr \
--to=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 \
/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).