From: Pratyush Yadav <me@yadavpratyush.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Robert Pollak <robert.pollak@posteo.net>,
Paul Mackerras <paulus@ozlabs.org>,
git@vger.kernel.org
Subject: Re: [RFC PATCH] gitk: Activate --find-copies-harder
Date: Mon, 11 Jan 2021 18:03:57 +0530 [thread overview]
Message-ID: <87mtxfwt3e.fsf@yadavpratyush.com> (raw)
In-Reply-To: <23445a9c-46b2-0232-845b-c8d5fe36d506@redhat.com> (Laszlo Ersek's message of "Mon, 11 Jan 2021 10:21:25 +0100")
On Mon, Jan 11 2021, Laszlo Ersek wrote:
> On 01/10/21 13:59, Robert Pollak wrote:
>> On 2021-01-06 16:58, Laszlo Ersek wrote:
>>> On 01/04/21 20:54, Robert Pollak wrote:
>> [...]
>>>> I see the following problems with my patch:
>>>>
>>>> 1) It is totally untested with all the other args that are collected in
>>>> diffargs, like e.g. "-O<orderfile>", since I didn't need them yet.
>>>
>>> It would be really great if gitk supported both "-O<orderfile>" and
>>> --find-copies-harder!
>>
>> Can you please test these options with my patch and report back?
>>
>> -- Robert
>>
>
> The patch doesn't apply with git-am (I'm trying on top of 72c4083ddf91):
>
>> Applying: gitk: Activate --find-copies-harder
>> error: corrupt patch at line 100
>> Patch failed at 0001 gitk: Activate --find-copies-harder
>> hint: Use 'git am --show-current-patch' to see the failed patch
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am --abort".
>
> One problem could be the embedded diff in the notes section (I guess it
> could confuse git-am).
>
> Also, "gitk" has existed at "gitk-git/gitk" since commit 62ba5143ec2a
> ("Move gitk to its own subdirectory", 2007-11-18), so the pathname
> headers in the patch look wrong.
gitk is maintained as a separate repo by Paul Mackerras at
git://ozlabs.org/~paulus/gitk, and then is pulled into the main Git repo
from time to time using a subtree merge. That's how gitk changes end up
in gitk-git/. Patches for gitk should be based on the gitk repo to make
it easier for Paul to apply them. In short, the paths are fine.
> Thanks
> Laszlo
>
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2021-01-11 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 19:54 [RFC PATCH] gitk: Activate --find-copies-harder Robert Pollak
2021-01-06 15:58 ` Laszlo Ersek
2021-01-10 12:59 ` Robert Pollak
2021-01-11 9:21 ` Laszlo Ersek
2021-01-11 12:33 ` Pratyush Yadav [this message]
2021-01-11 16:28 ` Laszlo Ersek
2021-01-11 21:00 ` Junio C Hamano
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=87mtxfwt3e.fsf@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=git@vger.kernel.org \
--cc=lersek@redhat.com \
--cc=paulus@ozlabs.org \
--cc=robert.pollak@posteo.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 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.