From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] update-index: there no longer is `apply --index-info`
Date: Wed, 8 Aug 2018 18:43:36 -0400 [thread overview]
Message-ID: <20180808224336.GB3902@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqva8kee3t.fsf@gitster-ct.c.googlers.com>
On Wed, Aug 08, 2018 at 02:35:18PM -0700, Junio C Hamano wrote:
> Back when we removed `git apply --index-info` in 2007, we forgot to
> adjust the documentation for update-index that reads its output.
>
> Let's reorder the description of three formats to present the other
> two formats that are still generated by git commands before this
> format, and stop mentioning `git apply --index-info`.
Yep, this makes sense.
> ---
> Documentation/git-update-index.txt | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
For fun, I tried out my "doc-diff" on it, and it looks good. :)
-Peff
prev parent reply other threads:[~2018-08-08 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 21:35 [PATCH] update-index: there no longer is `apply --index-info` Junio C Hamano
2018-08-08 22:43 ` Jeff King [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=20180808224336.GB3902@sigill.intra.peff.net \
--to=peff@peff.net \
--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).