From: Stefan Kangas <stefan@marxist.se>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 49065@debbugs.gnu.org, Filipp Gunbin <fgunbin@fastmail.fm>,
dick.r.chiang@gmail.com
Subject: bug#49065: 28.0.50; Major Changes to Gnus
Date: Mon, 20 Sep 2021 00:12:00 -0700 [thread overview]
Message-ID: <CADwFkmmCb=pzVeuZSC7NQFTeYO68rgkHoFFJ2ysoDCmxypDjmA@mail.gmail.com> (raw)
In-Reply-To: <875yuwujns.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> I think the update is that the bug reporter has forked Emacs entirely:
>
> https://github.com/dickmao/commercial-emacs
>
> Probably this bug report can be closed.
This code was offered to Emacs, so I don't think the fork is relevant.
We are still waiting to hear back from the original poster of this bug
report, to see if he is prepared to break this patch down into smaller
chunks. That would be by far the best outcome for Emacs, both the
original version and his fork. (It would, among other things, of course
make the work of maintaining his fork easier.)
If he can't or won't do that, perhaps there is someone else here who is
capable and willing to do that work. Perhaps there are features in
there that are indeed very useful. I don't know, but I feel like it
would at the very least be worth taking a look.
Only if both those options fail, should we close this bug report.
But that's just my opinion, of course.
next prev parent reply other threads:[~2021-09-20 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 17:57 bug#49065: 28.0.50; Major Changes to Gnus dick.r.chiang
2021-06-21 20:03 ` Filipp Gunbin
2021-06-21 20:39 ` Eric Abrahamsen
2021-09-19 16:52 ` Stefan Kangas
2021-09-20 1:20 ` Eric Abrahamsen
2021-09-20 7:12 ` Stefan Kangas [this message]
2021-09-21 22:15 ` Richard Stallman
2021-11-11 5:11 ` 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='CADwFkmmCb=pzVeuZSC7NQFTeYO68rgkHoFFJ2ysoDCmxypDjmA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=49065@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=eric@ericabrahamsen.net \
--cc=fgunbin@fastmail.fm \
/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).