From: Stefan Kangas <stefan@marxist.se>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
26028@debbugs.gnu.org, Arseny Sher <sher-ars@yandex.ru>,
Kaushal Modi <kaushal.modi@gmail.com>
Subject: bug#26028: 26.0.50; epatch for multifile patches
Date: Tue, 11 Aug 2020 00:34:55 -0700 [thread overview]
Message-ID: <CADwFkm=z=UdL+TJ9GVJdBAxS-BgsbHrxPb=gq4Hi7TbkuRc_5A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705240920300.30390@calancha-pc> (Tino Calancha's message of "Wed, 24 May 2017 09:46:59 +0900 (JST)")
Tino Calancha <tino.calancha@gmail.com> writes:
> On Wed, 24 May 2017, Michael Heerdegen wrote:
>
>> Tino Calancha <tino.calancha@gmail.com> writes:
>>
>>> Recently i am not using `epatch', but maybe following patch
>>> is of interest for someone:
>>
>> FWIW, do you think you understood all of the code you changed (I ask
>> because I gave up after a while)?
> I think so. I you exclude from the patch the added tests in
> test/lisp/vc/ediff-ptch-tests.el
> then this patch just touch:
> 2 files changed, 42 insertions(+), 18 deletions(-)
> The only it does:
> * tweak the original heuristic part for guessing the file names
> * change the suggested defaults in the prompts asking for the patch and
> dirs to patch.
>
>> If you did, do you think we should
>> install your fix, or are there open questions?
> I have tested with plain diffs and with Git diffs. I didn't test it
> with other VC than Git.
> I don't think solves all the problems, but at least it makes `epatch' usable for
> the most common multipatch situations.
That was 3 years ago.
It looks like this patch was never installed. Should it be?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-11 7:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 17:29 bug#26028: 26.0.50; epatch for multifile patches Arseny Sher
2017-03-08 19:17 ` Eli Zaretskii
2017-03-08 21:53 ` Arseny Sher
2017-03-09 1:41 ` Tino Calancha
2017-03-09 11:44 ` Arseny Sher
2017-05-23 11:26 ` Tino Calancha
2017-05-23 22:45 ` Michael Heerdegen
2017-05-24 0:46 ` Tino Calancha
2020-08-11 7:34 ` Stefan Kangas [this message]
2020-10-03 22:25 ` Michael Heerdegen
2021-05-10 12:02 ` Lars Ingebrigtsen
2021-05-12 9:27 ` Michael Heerdegen
2021-05-13 16:29 ` Filipp Gunbin
2021-05-16 13:57 ` Lars Ingebrigtsen
2021-07-23 12:54 ` Lars Ingebrigtsen
2022-03-24 8:34 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=z=UdL+TJ9GVJdBAxS-BgsbHrxPb=gq4Hi7TbkuRc_5A@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=26028@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=sher-ars@yandex.ru \
--cc=tino.calancha@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).