From: Jonathan Nieder <firstname.lastname@example.org>
To: Frederick Eaton <email@example.com>
Cc: Eric Sunshine <firstname.lastname@example.org>,
email@example.com, "Robert P. J. Day" <firstname.lastname@example.org>
Subject: Re: de-alphabetizing the documentation
Date: Fri, 6 Jul 2018 16:47:15 -0700 [thread overview]
Message-ID: <20180706234715.GA81694@aiede.svl.corp.google.com> (raw)
Frederick Eaton wrote:
> Unfortunately my contribution will have to be limited for the
> moment to making this suggestion, as I am extraordinarily busy. I hope
> it will not be too burdensome to add this item to your TODO list and
> keep it there until a willing volunteer comes along.
No problem. If you have time to contribute later, we can wait. :)
> For what it's worth, I made extensive changes to the Arch Wiki Git
> article back in 2015, following an initial attempt of mine to
> understand various tutorials. It was the most prominent wiki-based Git
> documentation I could find at the time. The article has of course seen
> numerous improvements since then.
For reference: https://wiki.archlinux.org/index.php/git
> I don't think that it's really important to find a "best" ordering for
> commands or glossary terms; it's more a matter of finding someone who
> is willing to take responsibility for choosing a reasonable ordering.
> Presumably the head maintainer of this project could delegate the task
> to a qualified volunteer, not a newbie like myself but not necessarily
> someone with expert knowledge either.
I'd have to say, when I compare the troubles a new user and a
long-timer would run into, I conclude that the long-timers would be
more likely to produce worse documentation. It is very difficult to
remember how new users see things. The ideal skill set in fact has
nothing to do with level of Git expertise: to produce a good result, a
good technical writer would ask the right questions to gather
information from the experts and then test their documentation on
newcomers until it works well.
Based on the work you've described already having done, it sounds like
you'd be an ideal person to get this going, if you find yourself with
time for it.
> It's too bad that a policy of
> not listing things alphabetically wasn't adopted from the beginning of
> this project, but I guess that's life.
From this thread I've been convinced that for this kind of reference
document, alphabetical organization within each section is a good
organization, provided each section is small enough (as in "git help"
I'm also a fan of non reference documentation that can use a narrative
ordering instead (like "git help core-tutorial", except with more
> Thanks Eric for the pointer to "git help". This does indeed provide a
> finer and better grouping than the man-page (but it also looks like
> another candidate for de-alphabetization...!).
Indeed, copying that organization over from "git help" to the git(1)
manpage may be a good step for any interested people overhearing this
As a first step, how about making git(1) recommend "git help", like
this? It already recommends giteveryday(7) but the more interactive
first command might be useful for some people.
-- >8 --
Subject: git doc: recommend "git help" as a starting point
The list of subcommands described in git(1) can be overwhelming.
Encourage newcomers to run "git help" to get a shorter list of
commands as a starting point.
Based on a suggestion by Frederick Eaton.
Signed-off-by: Jonathan Nieder <email@example.com>
Documentation/git.txt | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index dba7f0c18e..0149ce9af0 100644
@@ -23,9 +23,12 @@ unusually rich command set that provides both high-level operations
and full access to internals.
See linkgit:gittutorial to get started, then see
-linkgit:giteveryday for a useful minimum set of
-commands. The link:user-manual.html[Git User's Manual] has a more
+linkgit:giteveryday and run
+ git help
+for a useful minimum set of commands. The link:user-manual.html[Git
+User's Manual] has a more in-depth introduction.
After you mastered the basic concepts, you can come back to this
page to learn what commands Git offers. You can learn more about
next prev parent reply other threads:[~2018-07-06 23:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 20:04 de-alphabetizing the documentation frederik
2018-07-06 21:16 ` Jonathan Nieder
2018-07-06 21:18 ` Jonathan Nieder
2018-07-06 23:21 ` frederik
2018-07-06 23:47 ` Jonathan Nieder [this message]
2018-07-08 1:09 ` frederik
2018-07-24 19:52 ` frederik
2018-07-24 21:11 ` Jonathan Nieder
2018-08-11 2:30 ` frederik
2018-08-13 18:17 ` Junio C Hamano
2019-02-19 17:54 ` [PATCH 0/1] de-alphabetize command list Frederick Eaton
2019-02-21 18:05 ` frederik
2019-03-11 9:04 ` frederik
2019-03-11 14:38 ` Jacob Keller
2019-02-19 17:54 ` [PATCH] Prioritize list of commands appearing in git(1), via command-list.txt. Don't invoke 'sort' in Documentation/cmd-list.perl Frederick Eaton
2018-07-07 4:25 ` de-alphabetizing the documentation Theodore Y. Ts'o
2018-07-06 21:32 ` Eric Sunshine
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).