From: Johannes Altmanninger <aclopte@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: newren@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH v2 4/4] Documentation/git-status: mention how to detect copies
Date: Tue, 5 Oct 2021 21:42:24 +0200 [thread overview]
Message-ID: <20211005194224.qcblxih5rlehzo4d@gmail.com> (raw)
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.
next prev parent reply other threads:[~2021-10-05 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 21:30 [PATCH 1/2] Documentation/diff-format: state in which cases porcelain status is T Johannes Altmanninger
2021-10-02 21:30 ` [PATCH 2/2] Documentation/git-status: document porcelain status T (typechange) Johannes Altmanninger
2021-10-02 21:33 ` Johannes Altmanninger
2021-10-02 23:29 ` Elijah Newren
2021-10-04 18:57 ` Johannes Altmanninger
2021-10-04 19:00 ` [PATCH v2 1/4] Documentation/git-status: remove impossible porcelain status DR and DC Johannes Altmanninger
2021-10-04 19:00 ` [PATCH v2 2/4] Documentation/diff-format: state in which cases porcelain status is T Johannes Altmanninger
2021-10-04 19:00 ` [PATCH v2 3/4] Documentation/git-status: document porcelain status T (typechange) Johannes Altmanninger
2021-10-04 19:00 ` [PATCH v2 4/4] Documentation/git-status: mention how to detect copies Johannes Altmanninger
2021-10-05 9:48 ` Bagas Sanjaya
2021-10-05 19:42 ` Johannes Altmanninger [this message]
2021-10-06 5:05 ` Bagas Sanjaya
2021-10-06 6:04 ` Elijah Newren
2021-10-04 20:02 ` [PATCH v2 1/4] Documentation/git-status: remove impossible porcelain status DR and DC Junio C Hamano
2021-10-04 20:12 ` Junio C Hamano
2021-10-02 23:35 ` [PATCH 1/2] Documentation/diff-format: state in which cases porcelain status is T Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211005194224.qcblxih5rlehzo4d@gmail.com \
--to=aclopte@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).