Re: [PATCH v4 2/3] docs: improve send-email documentation

From: Aditya Garg <gargaditya08@live.com>
Date: May 8, 2025, 15:08 UTC
Message-ID: <PN3PR01MB9597E7D76464369382B38B53B88BA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <PN3PR01MB959761BC7EF27EE2CFB1134BB88BA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>

Show 32 quoted lines

> On 8 May 2025, at 8:35 PM, Aditya Garg <gargaditya08@live.com> wrote:
> 
> 
> 
>> On 8 May 2025, at 8:23 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> 
>> Junio C Hamano <gitster@pobox.com> writes:
>> 
>>>> I think ~/.gitconfig should be in single quotes, its not a command.
>>> 
>>> "Is this something the end-user would type verbatim?" is the criteria,
>>> not "Is this a command name?".
>> 
>> Looking for "^Markup:" in Documentation/CodingGuidelines, we find a
>> better description.
>> 
>> Literal parts (e.g. use of command-line options, command names,
>> branch names, URLs, pathnames (files and directories), configuration and
>> environment variables) must be typeset as verbatim (i.e. wrapped with
>> backticks):
>>  `--pretty=oneline`
>>  `git rev-list`
>>  `remote.pushDefault`
>>  `http://git.example.com`
>>  `.git/config`
>>  `GIT_DIR`
>>  `HEAD`
>>  `umask`(2)
>> 
> 
> I see. Since you have already queued the v5, can you do this change on your end,
> or should I send a v6?

Guess what, I'll just send a version 6. Its not a big change.