From: Scott Chacon <schacon@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
"David E. Wheeler" <david@justatheory.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: Bad Man Page URLs
Date: Thu, 26 Apr 2012 14:58:47 -0700 [thread overview]
Message-ID: <CAP2yMa+mjvFmVwXjrB7FRaD2=iMCCPENWAOoCG5TCsqFdsCDxQ@mail.gmail.com> (raw)
In-Reply-To: <20120426210251.GA31589@sigill.intra.peff.net>
Hey,
On Thu, Apr 26, 2012 at 2:02 PM, Jeff King <peff@peff.net> wrote:
>>
>> Do you know of a public webpage we can count on to continue to serve
>> the docs? I agree that that would be even better.
>
> I think http://git-scm.com/ would be the ideal place. My understanding
> is that the re-work of the site is nearing completion. Scott, ETA?
Yes, we are very close to launching a big redesign of git-scm.com.
The manpages will be automatically updated on that site, you can
certainly link to them there.
If you want to preview what it's going to look like and the URL
structure, you can check out the current working version here:
http://git-scm.herokuapp.com/docs/git-fetch
There are a number of known bugs and I want to make it much faster
before I officially launch it and redirect DNS, but you can get an
idea of how it will be structured and what it will look like. If you
want to start generating docs with static urls for man pages, they can
be of the form: http://git-scm.com/docs/git-command
You can also put a version number after them to permalink them at a
certain version:
http://git-scm.herokuapp.com/docs/git-fetch/1.7.3.2
When it's close to what I think is ready, I'll do a post to this list
looking for feedback and bugs, etc.
Scott
>
> -Peff
next prev parent reply other threads:[~2012-04-26 21:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 1:48 Bad Man Page URLs David E. Wheeler
2012-04-06 2:32 ` Jeff King
2012-04-06 2:54 ` Jeff King
2012-04-06 4:22 ` Jonathan Nieder
2012-04-06 5:46 ` Jeff King
2012-04-06 6:17 ` Jonathan Nieder
2012-04-06 7:15 ` Junio C Hamano
2012-04-06 7:23 ` Jeff King
2012-04-26 20:12 ` David E. Wheeler
2012-04-26 20:19 ` Jonathan Nieder
2012-04-26 20:24 ` David E. Wheeler
2012-04-26 20:29 ` Jonathan Nieder
2012-04-26 20:34 ` David E. Wheeler
2012-05-02 21:46 ` Jakub Narebski
2012-04-26 21:02 ` Jeff King
2012-04-26 21:58 ` Scott Chacon [this message]
2012-04-26 22:11 ` David E. Wheeler
2012-04-26 22:12 ` Jonathan Nieder
2012-04-26 22:16 ` Junio C Hamano
2012-04-26 22:25 ` Scott Chacon
2012-04-26 22:34 ` Jonathan Nieder
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='CAP2yMa+mjvFmVwXjrB7FRaD2=iMCCPENWAOoCG5TCsqFdsCDxQ@mail.gmail.com' \
--to=schacon@gmail.com \
--cc=david@justatheory.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).