git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Aguilar <davvid@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: minor consistency fixes in   git-difftool.txt.
Date: Wed, 25 Mar 2009 11:21:38 +0100	[thread overview]
Message-ID: <49CA05B2.7020207@drmicha.warpmail.net> (raw)
In-Reply-To: <7vocvq842a.fsf@gitster.siamese.dyndns.org>

Junio C Hamano venit, vidit, dixit 25.03.2009 08:17:
> David Aguilar <davvid@gmail.com> writes:
> 
>> Signed-off-by: David Aguilar <davvid@gmail.com>
>> ---
>>  Documentation/git-difftool.txt |    6 +++---
>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/git-difftool.txt b/Documentation/git-difftool.txt
>> index 5ae02f8..23070c1 100644
>> --- a/Documentation/git-difftool.txt
>> +++ b/Documentation/git-difftool.txt
>> @@ -12,7 +12,7 @@ SYNOPSIS
>>  DESCRIPTION
>>  -----------
>>  'git-difftool' is a git command that allows you to compare and edit files
>> -between revisions using common diff tools.  'git difftool' is a frontend
>> +between revisions using common diff tools.  'git-difftool' is a frontend
> 
> I thought that the recent trend is to spell these as 'git difftool' (two
> separate words), although I didn't follow the discussion on quoting styles
> closely, so I do not know which of sq, dq or backtick is preferred.
> 
> Can somebody help me out here?
> 

I'd say it's backticks for commands/code, but I think discussion about a
style guide is still on.

Michael

  reply	other threads:[~2009-03-25 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  6:14 [PATCH] Documentation: minor consistency fixes in git-difftool.txt David Aguilar
2009-03-25  7:17 ` Junio C Hamano
2009-03-25 10:21   ` Michael J Gruber [this message]
2009-03-26  4:17     ` David Aguilar

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=49CA05B2.7020207@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).