Re: [RFC/PATCH 1/8] user-manual: remove some git-foo usage

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Mar 23, 2009, 10:54 UTC
Message-ID: <94a0d4530903230354x3a37cf56oe3862c2b7c37a8d4@mail.gmail.com>
In-Reply-To: <20090323063141.GA1119@coredump.intra.peff.net>

On Mon, Mar 23, 2009 at 8:31 AM, Jeff King <peff@peff.net> wrote:

Show 24 quoted lines

> On Sun, Mar 22, 2009 at 08:05:14PM +0200, Felipe Contreras wrote:
>
>>  Every commit has a 40-hexdigit id, sometimes called the "object name" or the
>> -"SHA1 id", shown on the first line of the "git-show" output.  You can usually
>> +"SHA1 id", shown on the first line of the "git show" output.  You can usually
>
> I think some of these were intentionally left in the original mass
> dashes to spaces conversion. The intent was that one could use the
> git-show form in talking about the command in text.
>
> However, I think I actually prefer the version given by your patch. I
> just wanted to point out that this is a decision to change how we
> mention these in the documentation and not simply a fix for things that
> got missed in the conversion. Others may disagree on how it looks.
>
> It seems like you added monospace backticks in most locations. Is there
> a reason not to standardize on that and use `git show` here?
>
>>  [[Updating-a-repository-With-git-fetch]]
>> -Updating a repository with git-fetch
>> +Updating a repository with git fetch
>>  ------------------------------------
>
> I think this one should probably be `git fetch`.

A subsequent patch is adding the monospace backticks and a lot more quotation stuff.

In this patch I tried to focus on git-foo, and add the backticks only when there are no delimiters, so I replaced "git-foo" with "git foo" and git-foo with `git foo`. I also didn't add backticks on the titles because I thought it was a bit controversial and was probably better in a separate patch.

Cheers.

-- 
Felipe Contreras