From: Johannes Altmanninger <aclopte@gmail.com>
Date: Tue, 05 Oct 2021 19:42:24 GMT
Subject: Re: [PATCH v2 4/4] Documentation/git-status: mention how to detect copies
Message-ID: <20211005194224.qcblxih5rlehzo4d@gmail.com>
In-Reply-To: <31f46980-7e40-46c0-87b7-f5ea7034af2b@gmail.com>

On Tue, Oct 05, 2021 at 04:48:00PM +0700, Bagas Sanjaya wrote:
> On 05/10/21 02.00, Johannes Altmanninger wrote:
> > -* 'C' = copied
> > +* 'C' = copied (if config option status.renames is set to "copies")
> 
> The config name and value can be formatted to monospace ("`status.renames`"
> and "`copies`" respectively).

I wasn't sure whether to add backticks to status.renames because we are
already inconsistent in this file (search for "config option").
Anyway I agree that backticks look better here (makes it bold in the man page).

Maybe we should automate this? We can write a test that makes sure that we
always use backticks around config keys, at least for new changes.

---

I didn't add backticks to "copies" to be consistent with this part before the context

	Ignore changes to submodules when looking for changes. <when> can be
	either "none", "untracked", "dirty" or "all", which is the default.