git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: git@vger.kernel.org, Thomas Ackermann <th.acker@arcor.de>
Subject: Re: Outdated and broken online versions of user-manual.html
Date: Mon, 20 May 2013 00:24:39 -0700	[thread overview]
Message-ID: <20130520072439.GF2919@elie.Belkin> (raw)
In-Reply-To: <BE32A698F2774BD5B5235264B13A46C8@PhilipOakley>

Philip Oakley wrote:
> From: "Thomas Ackermann" <th.acker@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 the shorter documents - one
> can't eat a whole melon in one bite ;-)

Yes.

Once there was a lovely file at

	Documentation/howto/isolate-bugs-with-bisect.txt

explaining how to use "git bisect" to find which commit caused a
kernel regression.  That it was a small independent file that didn't
assume the reader had read much before was very helpful, since it
meant people could easily point novices to that page and say "It's
easy!" when asking them to track down a bug.

Nowadays that content is gracefully included in the user-manual under
the heading [[using-bisect]].  But I never point people to it any more;
I just write out the steps by hand, to avoid intimidating them.

Ideally this content would be in an EXAMPLE or TUTORIAL section of the
git-bisect(1) manpage for easier reference.

Thanks,
Jonathan

      reply	other threads:[~2013-05-20  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 19:02 Outdated and broken online versions of user-manual.html W. Trevor King
2013-05-11  7:48 ` Thomas Ackermann
2013-05-11 11:36   ` Philip Oakley
2013-05-20  7:24     ` Jonathan Nieder [this message]

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=20130520072439.GF2919@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.org \
    --cc=th.acker@arcor.de \
    /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).