From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 26028@debbugs.gnu.org, Kaushal Modi <kaushal.modi@gmail.com>,
Stefan Kangas <stefan@marxist.se>,
Arseny Sher <sher-ars@yandex.ru>,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#26028: 26.0.50; epatch for multifile patches
Date: Mon, 10 May 2021 14:02:17 +0200 [thread overview]
Message-ID: <87v97qre46.fsf@gnus.org> (raw)
In-Reply-To: <87wo07c5gb.fsf@web.de> (Michael Heerdegen's message of "Sun, 04 Oct 2020 00:25:40 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> AFAIR it solved my problem, but I can't judge whether it's ok to
> install since I don't know the code.
The patch no longer applies cleanly -- do you have an up-to-date version
of Tino's patch in your tree, by any chance? Or did you just try it
then, and then back it out again?
Looking at the commit history for ediff, it doesn't really look like we
have any ediff domain experts to evaluate the patch, which makes it hard
to decide whether to try to apply the patch or not.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-10 12:02 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
2020-10-03 22:25 ` Michael Heerdegen
2021-05-10 12:02 ` Lars Ingebrigtsen [this message]
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=87v97qre46.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26028@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=sher-ars@yandex.ru \
--cc=stefan@marxist.se \
--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).