From: "David E. Wheeler" <david@justatheory.com>
To: Scott Chacon <schacon@gmail.com>
Cc: Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: Bad Man Page URLs
Date: Thu, 26 Apr 2012 15:11:52 -0700 [thread overview]
Message-ID: <BEA084BA-739D-4D73-80C0-FE2FC1598D9F@justatheory.com> (raw)
In-Reply-To: <CAP2yMa+mjvFmVwXjrB7FRaD2=iMCCPENWAOoCG5TCsqFdsCDxQ@mail.gmail.com>
On Apr 26, 2012, at 2:58 PM, Scott Chacon wrote:
> 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
Wow, the new site looks *awesome*! :-)
> 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
Very nice. I only found one of the links from the manpage there, though:
Everyday Git
http://git-scm.herokuapp.com/docs/everyday.html
Here are the others on gitmanual.org (maybe I just couldn't find them on the new site?):
User Manual
http://www.gitmanual.org/user-manual.html
git concepts chapter of the user-manual
http://www.gitmanual.org/user-manual.html#git-concepts
howto
http://www.gitmanual.org/howto-index.html
And this one is a broken link on gitmanual.org and other places on the internetz.
GIT API documentation
????
Best,
David
next prev parent reply other threads:[~2012-04-26 22:12 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
2012-04-26 22:11 ` David E. Wheeler [this message]
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=BEA084BA-739D-4D73-80C0-FE2FC1598D9F@justatheory.com \
--to=david@justatheory.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--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 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.