From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: git-scm.com refresh
Date: Sun, 06 May 2012 00:10:26 -0500 [thread overview]
Message-ID: <4FA607C2.6030906@gmail.com> (raw)
In-Reply-To: <CAP2yMaJy=1c3b4F72h6jL_454+0ydEQNXYiC6E-ZeQQgE0PcVA@mail.gmail.com>
On 5/4/2012 6:29 PM, Scott Chacon wrote:
>
> I just shipped a big update to the git-scm.com website...
>
Thanks for the cool website, old and new! :)
> * There is now permanent man page hosting here, for example:
> http://git-scm.com/docs/git-fsck. You can also reference any older
> version of any command: http://git-scm.com/docs/git-fsck/1.5.5
>
IMO, I think the reference manual before the kernel.org crash was the
best. Back then, you first got a list of all the versions and you
picked your version. If I'm on version x I want to click on version x
one time for the entire refman, not for every manpage.
I prefer the git.git make doc version of the html. If you could have a
'classic' view of the reference manual that would be great. I'm not an
expert on the make doc technologies, but if your version is harder to
get working then a classic view would enable you to quickly and reliably
publish updates while ironing out the enhanced version.
Also, the new format has *way* too much whitespace on the sides for the
manpages. (Progit also has too much whitespace -- was it like that
before?) The manpages are long enough without double column width in a
single column. ;) The related topics is interesting. I think this
hybrid reference manual format should be called 'enhanced' or something.
I think its important to keep the official git reference manual
clearly distinguished from supplemental material because some of the
supplements are not correct (ie, [a]progit merge=ours). I think the new
hybrid format disguised as the reference manual will cause the newsgroup
to get alot of questions about supplemental material confused with the
reference manual pages. They probably already spend too much time
correcting my bum scoop posts as it is. ;)
I'm not a website expert, but an option to pick a stylesheet that has a
main theme color of blue, green, etc., as opposed to red-orange that
would a big plus in keeping with the open source concept. I'm not a
visual brain scientist, but I think my aversion to staring at a
red-orange website all the time has something to do with why walls are
not normally painted red-orange either. ;)
> * There are still a few asciidoc parsing issues that we're working on
> - if you find anything that's weird please report it at our issue
> tracker: https://github.com/github/gitscm-next/issues
>
git-rebase manpage is pretty hosed. (when i tried to report on github
it wanted me to signup.)
Footnotes:
a. http://git-scm.com/book/en/Customizing-Git-Git-Attributes,
http://comments.gmane.org/gmane.comp.version-control.git/192798
v/r,
neal
next prev parent reply other threads:[~2012-05-06 5:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 23:29 git-scm.com refresh Scott Chacon
2012-05-05 0:26 ` Jakub Narebski
2012-05-05 22:24 ` Scott Chacon
2012-05-05 23:20 ` Josh Juran
2012-05-05 1:31 ` Junio C Hamano
2012-05-05 16:47 ` Felipe Contreras
2012-05-05 22:38 ` Scott Chacon
2012-05-06 1:39 ` Junio C Hamano
2012-05-06 2:31 ` Felipe Contreras
2012-05-06 3:51 ` Scott Chacon
2012-05-06 8:33 ` Philip Oakley
2012-05-07 17:06 ` Junio C Hamano
2012-05-08 16:51 ` Junio C Hamano
2012-05-08 17:46 ` Andreas Schwab
2012-05-08 18:00 ` Junio C Hamano
2012-05-05 9:14 ` Andrew Sayers
2012-05-05 14:01 ` Felipe Contreras
2012-05-05 14:36 ` Philip Oakley
2012-05-06 0:08 ` Neal Kreitzinger
2012-05-06 5:10 ` Neal Kreitzinger [this message]
2012-05-06 11:04 ` Matthieu Moy
2012-05-06 13:36 ` Scott Chacon
2012-05-07 4:18 ` Christian Couder
2012-05-07 17:08 ` Ævar Arnfjörð Bjarmason
2012-05-07 15:08 ` A Large Angry SCM
2012-05-07 21:04 ` Matthieu Moy
2012-05-09 22:13 ` Heiko Voigt
2012-05-08 12:29 ` Antonio Ospite
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=4FA607C2.6030906@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--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).