git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benoit Sigoure <tsuna@lrde.epita.fr>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
	Lars Hjemli <hjemli@gmail.com>,
	Jonas Juselius <jonas.juselius@chem.uit.no>,
	git@vger.kernel.org
Subject: Re: Git in a Nutshell guide
Date: Mon, 19 Nov 2007 17:23:05 -0500	[thread overview]
Message-ID: <20071119222305.GE22293@fieldses.org> (raw)
In-Reply-To: <0E0AA90A-2282-4AFE-8B94-EA0E35B57D65@lrde.epita.fr>

On Mon, Nov 19, 2007 at 10:51:35PM +0100, Benoit Sigoure wrote:
> On Nov 19, 2007, at 10:33 PM, Matthieu Moy wrote:
>
>> Benoit Sigoure <tsuna@lrde.epita.fr> writes:
>>
>>> No please stop adding links from on man page to another.  If you read
>>> man git-reflog, you surely want to learn the HEAD@{N} syntax and see
>>> practical uses cases.
>>
>> I don't understand your point.
>>
>> Yes, if I read man git-reflog, I do surely want to learn HEAD@{N}
>> syntax, but that is _precisely_ what my patch does.
>
> By telling you to read another man page which is annoying and a recurring 
> complaint.

Are we looking at the same patch?  It both gives examples of the syntax
*and* refers to another page.  I thought it was the lack of the former,
rather than the presence of the latter, that was the recurring
complaint....

--b.

  reply	other threads:[~2007-11-19 22:23 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 13:05 Git in a Nutshell guide Jonas Juselius
2007-11-19 13:29 ` Jakub Narebski
2007-11-19 14:33   ` Jonas Juselius
2007-11-22  8:22   ` David Kågedal
2007-11-23  9:28     ` Jakub Narebski
2007-11-19 15:02 ` Brian Downing
2007-11-19 15:03   ` Brian Downing
2007-11-19 15:48   ` Nicolas Pitre
2007-11-19 16:05 ` Jakub Narebski
2007-11-19 16:14   ` Jonas Juselius
2007-11-19 16:49     ` Benoit Sigoure
2007-11-19 22:01       ` Daniel Barkalow
2007-11-20 11:34       ` Jonas Juselius
2007-11-20 23:57       ` Jakub Narebski
2007-11-21 19:45         ` Jan Hudec
2007-11-21 21:32           ` Jakub Narebski
2007-11-22 16:37             ` jhud7196
2007-11-22 13:15   ` Jonas Juselius
2007-11-22 14:19     ` Jonathan del Strother
2007-11-22 14:24     ` Johannes Schindelin
2007-11-22 16:57     ` jhud7196
2007-11-19 16:45 ` Lars Hjemli
2007-11-19 16:56   ` Jonas Juselius
2007-11-19 16:57   ` Benoit Sigoure
2007-11-19 17:04     ` Lars Hjemli
2007-11-19 18:10       ` Benoit Sigoure
2007-11-19 18:13         ` J. Bruce Fields
2007-11-19 18:13         ` Matthieu Moy
2007-11-19 18:35           ` [PATCH] Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys Matthieu Moy
2007-11-19 20:13             ` Junio C Hamano
2007-11-19 20:28               ` Matthieu Moy
2007-11-19 20:31                 ` Matthieu Moy
2007-11-19 21:15           ` Git in a Nutshell guide Benoit Sigoure
2007-11-19 21:33             ` Matthieu Moy
2007-11-19 21:51               ` Benoit Sigoure
2007-11-19 22:23                 ` J. Bruce Fields [this message]
2007-11-19 22:29                 ` Junio C Hamano
2007-11-19 22:59                   ` Matthieu Moy
2007-11-19 23:07                     ` Junio C Hamano
2007-11-19 17:05     ` Matthieu Moy

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=20071119222305.GE22293@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=jonas.juselius@chem.uit.no \
    --cc=tsuna@lrde.epita.fr \
    /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).