From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: gitster@pobox.com, git@vger.kernel.org,
Alastair McGowan-Douglas <altreus@altre.us>
Subject: Re: [PATCH 1/3] Documentation: use 'keyid' consistantly, not 'key-id'
Date: Fri, 18 Sep 2015 15:23:45 -0400 [thread overview]
Message-ID: <20150918192345.GD11068@sigill.intra.peff.net> (raw)
In-Reply-To: <1442588510-7379-2-git-send-email-Matthieu.Moy@imag.fr>
On Fri, Sep 18, 2015 at 05:01:48PM +0200, Matthieu Moy wrote:
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
> ---
> Documentation/git-cherry-pick.txt | 4 ++--
> Documentation/git-revert.txt | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Hmm, grepping for `key-id` turns up quite a few more hits. Is there any
reason not to change those, too?
-Peff
next prev parent reply other threads:[~2015-09-18 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 9:44 git status -u is mildly astonishing Alastair McGowan-Douglas
2015-09-17 14:27 ` Matthieu Moy
2015-09-17 17:43 ` Jeff King
2015-09-18 6:52 ` Matthieu Moy
2015-09-18 15:01 ` [PATCH 0/3] Clarify the documentation of options with optional arguments Matthieu Moy
2015-09-18 15:01 ` [PATCH 1/3] Documentation: use 'keyid' consistantly, not 'key-id' Matthieu Moy
2015-09-18 15:24 ` Matthieu Moy
2015-09-18 19:23 ` Jeff King [this message]
2015-09-18 15:01 ` [PATCH 2/3] Documentation/grep: fix documentation of -O Matthieu Moy
2015-09-18 15:01 ` [PATCH 3/3] Documentation: make explicit that optional arguments must be stuck Matthieu Moy
2015-09-18 19:27 ` Jeff King
2015-09-19 7:47 ` [PATCH v2 0/3] Clarify the documentation of options with optional arguments Matthieu Moy
2015-09-19 7:47 ` [PATCH v2 1/3] Documentation: use 'keyid' consistently, not 'key-id' Matthieu Moy
2015-09-19 7:47 ` [PATCH v2 2/3] Documentation/grep: fix documentation of -O Matthieu Moy
2015-09-19 7:47 ` [PATCH v2 3/3] Documentation: explain optional arguments better Matthieu Moy
2015-09-19 10:50 ` [PATCH v2 0/3] Clarify the documentation of options with optional arguments Jeff King
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=20150918192345.GD11068@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@imag.fr \
--cc=altreus@altre.us \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).