From: Eric Sunshine <email@example.com> To: "Martin Ågren" <firstname.lastname@example.org> Cc: Git Mailing List <email@example.com>, Duy Nguyen <firstname.lastname@example.org>, Junio C Hamano <email@example.com>, Taylor Blau <firstname.lastname@example.org> Subject: Re: [PATCH v2 0/5] git-worktree documentation cleanups Date: Tue, 4 Aug 2020 00:44:23 -0400 [thread overview] Message-ID: <CAPig+cS2jsmYkpf5+Kob2w09UKQgBvM5wjOV-bS-fVOK5KGhyA@mail.gmail.com> (raw) In-Reply-To: <CAN0heSpO4ocUTv2BSAOkRsuEX59V7phKn1=Y-PU2qq0POhp1Rg@mail.gmail.com> On Tue, Aug 4, 2020 at 12:29 AM Martin Ågren <email@example.com> wrote: > On Tue, 4 Aug 2020 at 02:56, Eric Sunshine <firstname.lastname@example.org> wrote: > > git-wortkree.txt: link to man pages when citing other Git commands > > s/wortkree/worktree/ in the subject of the final, new patch. Thanks. Perhaps Junio can tweak that when queuing, otherwise I'll fix it if I re-roll, otherwise it's minor enough that I won't worry about it if it makes it into permanent history. > I agree with all changes since v1, except ... > > > -By default, the repository "config" file is shared across all working > > +By default, the repository `config` file is shared across all working > > I don't think this is a filename (in which case it would have been > `.gitconfig?) but rather some sort of colloquial short form for > 'configuration file', thus '"config" file'. So I could see the double > quotes remain or being dropped, but I was surprised to see them > converted like this. I also thought at first that it was just shorthand for "configuration file", but then I realized that it's talking about the `.git/config` file, in which case it is an actual filename. So, I believe that quoting it with backticks is correct here.
next prev parent reply other threads:[~2020-08-04 4:44 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-03 5:36 [PATCH 0/4] " Eric Sunshine 2020-08-03 5:36 ` [PATCH 1/4] git-worktree.txt: employ fixed-width typeface consistently Eric Sunshine 2020-08-03 5:36 ` [PATCH 2/4] git-worktree.txt: consistently use term "working tree" Eric Sunshine 2020-08-03 5:36 ` [PATCH 3/4] git-worktree.txt: fix minor grammatical issues Eric Sunshine 2020-08-03 5:36 ` [PATCH 4/4] git-worktree.txt: make start of new sentence more obvious Eric Sunshine 2020-08-03 16:11 ` [PATCH 0/4] git-worktree documentation cleanups Taylor Blau 2020-08-03 17:14 ` Junio C Hamano 2020-08-03 17:57 ` Martin Ågren 2020-08-03 23:54 ` Eric Sunshine 2020-08-04 0:15 ` Junio C Hamano 2020-08-04 0:55 ` [PATCH v2 0/5] " Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 1/5] git-worktree.txt: employ fixed-width typeface consistently Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 2/5] git-worktree.txt: consistently use term "working tree" Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 3/5] git-worktree.txt: fix minor grammatical issues Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 4/5] git-worktree.txt: make start of new sentence more obvious Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 5/5] git-wortkree.txt: link to man pages when citing other Git commands Eric Sunshine 2020-08-04 1:10 ` [PATCH v2 0/5] git-worktree documentation cleanups Taylor Blau 2020-08-04 4:28 ` Martin Ågren 2020-08-04 4:44 ` Eric Sunshine [this message] 2020-08-04 5:23 ` Martin Ågren
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=CAPig+cS2jsmYkpf5+Kob2w09UKQgBvM5wjOV-bS-fVOK5KGhyA@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2 0/5] git-worktree documentation cleanups' \ /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
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).