From: Sam James <sam@gentoo.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3 0/2] diff: copies-harder support
Date: Tue, 16 Apr 2024 03:42:13 +0100 [thread overview]
Message-ID: <87sezm1116.fsf@gentoo.org> (raw)
In-Reply-To: <875xwr27le.fsf@gentoo.org> (Sam James's message of "Mon, 08 Apr 2024 16:32:29 +0100")
Sam James <sam@gentoo.org> writes:
> Sam James <sam@gentoo.org> writes:
>
>> range-diff:
>> ```
>> [...]
>> ```
>>
>> Sam James (2):
>> diff: implement config.diff.renames=copies-harder
>> diff: whitespace cleanup
>>
>
> It was pointed out that
> https://github.com/gitgitgadget/git/pull/1606#issuecomment-2002137907
> that I forgot to add the changes in v2/v3.
>
> v2: Documentation phrasing fixes.
> v3: Split out whitespace & formatting changes into their own commit and
> apply missed documentation phrasing tweaks.
ping
I'm not sure of the etiquette for git development, so if it's too short
to ping, my apologies.
>
>
>> Documentation/config/diff.txt | 8 +++++---
>> Documentation/config/status.txt | 4 +++-
>> diff.c | 14 +++++++++++---
>> diff.h | 1 +
>> diffcore-rename.c | 6 ++++--
>> merge-ort.c | 2 +-
>> merge-recursive.c | 2 +-
>> 7 files changed, 26 insertions(+), 11 deletions(-)
next prev parent reply other threads:[~2024-04-16 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 21:38 [PATCH v3 0/2] diff: copies-harder support Sam James
2024-03-11 21:38 ` [PATCH v3 1/2] diff: implement config.diff.renames=copies-harder Sam James
2024-03-11 21:38 ` [PATCH v3 2/2] diff: whitespace cleanup Sam James
2024-04-08 15:32 ` [PATCH v3 0/2] diff: copies-harder support Sam James
2024-04-16 2:42 ` Sam James [this message]
2024-05-15 22:27 ` Sam James
2024-05-16 15:36 ` Junio C Hamano
2024-05-17 3:38 ` Sam James
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=87sezm1116.fsf@gentoo.org \
--to=sam@gentoo.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.