Philip Oakley wrote:
From: Thomas Ackermann th.ac...@arcor.de
(5) Large overlapping with the tutorials. IMHO all of the
tutorials should be blended into user-manual
[...]
I would be a little cautious of your point 5 if it squoze everything into
one overlong document at the expense of losing
W. Trevor King wking at tremily.us writes:
I'm also surprised that I couldn't find a more obvious link to the
manual from git-scm.com (I ended up taking a “See Also” link from
gittutorial(7) [3]). I'm not sure if this is intentional or not,
since git-scm.com does prominently link Pro Git,
From: Thomas Ackermann th.ac...@arcor.de
Sent: Saturday, May 11, 2013 8:48 AM
W. Trevor King wking at tremily.us writes:
I'm also surprised that I couldn't find a more obvious link to the
manual from git-scm.com (I ended up taking a “See Also” link from
gittutorial(7) [3]). I'm not sure if
(1) Very poor html formatting (document type book causes
ugly TOCs per section and there's a Part I without a Part II)
(2) Partly outdated content
(3) Sub-optimal structuring (to-do list as part of the document,
glossary not at the end of the document)
(4) User-manual.PDF uses an
I went to reference some `rebase -i` discussion that landed in 3ca26e8
(Merge branch 'wk/user-manual', 2013-02-25), and I couldn't find a
version of the manual online that contained the new content. There's
a version on kernel.org [1], but that doesn't seem to have been
updated since February.
5 matches
Mail list logo
