From: Robert Karszniewicz <avoidr@posteo.de>
To: Taylor Blau <me@ttaylorr.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] doc/git-branch: fix awkward wording for "-c"
Date: Thu, 4 Feb 2021 02:21:59 +0100 [thread overview]
Message-ID: <YBtMN91HMmVE9JTe@HP> (raw)
In-Reply-To: <YBsR+DALwV4Xxgvf@nand.local>
On Wed, Feb 03, 2021 at 04:13:28PM -0500, Taylor Blau wrote:
> On Wed, Feb 03, 2021 at 04:07:32PM -0500, Jeff King wrote:
> > The description for "-c" is hard to parse. I think the big issue is lack
> > of commas, but I've also reordered the words to keep the main focus
> > point of "instead of renaming, copy" together.
> >
> > Signed-off-by: Jeff King <peff@peff.net>
>
> Much clearer, thanks. I'm only responding to acknowledge that it reads
> more clearly to me, too.
I second that, much better. Thanks.
prev parent reply other threads:[~2021-02-04 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 21:07 [PATCH] doc/git-branch: fix awkward wording for "-c" Jeff King
2021-02-03 21:13 ` Taylor Blau
2021-02-04 1:21 ` Robert Karszniewicz [this message]
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=YBtMN91HMmVE9JTe@HP \
--to=avoidr@posteo.de \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).