git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Santi Béjar" <sbejar@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] user-manual.txt: Some doc updates
Date: Thu, 19 Apr 2007 12:07:01 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0704191205420.4504@xanadu.home> (raw)
In-Reply-To: <20070419160235.GE9101@fieldses.org>

On Thu, 19 Apr 2007, J. Bruce Fields wrote:

> It was a conscious decision to use a mixture of the two techniques; see,
> e.g.,
> 
> 	http://marc.info/?l=git&m=116994435503452&w=2
> 
> and followups.

Maybe it should be said more explicitly that both are fine.


Nicolas

  reply	other threads:[~2007-04-19 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 15:49 [PATCH] user-manual.txt: Some doc updates Santi Béjar
2007-04-19 16:02 ` J. Bruce Fields
2007-04-19 16:07   ` Nicolas Pitre [this message]
2007-04-19 17:01     ` J. Bruce Fields
2007-04-19 19:51       ` Santi Béjar
2007-05-08  3:21 ` J. Bruce Fields
2007-05-08  8:37   ` Santi Béjar

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=alpine.LFD.0.98.0704191205420.4504@xanadu.home \
    --to=nico@cam.org \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=sbejar@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).