From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Kangas <stefan@marxist.se>
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: Sun, 19 Sep 2021 18:20:55 -0700 [thread overview]
Message-ID: <875yuwujns.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CADwFkmnad7Y7F=pEH8sBh+EnE0Osg2=qHgZnxq_kpK108nW1+g@mail.gmail.com> (Stefan Kangas's message of "Sun, 19 Sep 2021 09:52:10 -0700")
Stefan Kangas <stefan@marxist.se> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Filipp Gunbin <fgunbin@fastmail.fm> writes:
>>
>>> It'd be more helpful to submit this in series of small-to-middle
>>> patches. It's very hard to review a "patch bomb"...
>>
>> +1. You're stuck with the code reviewers you've got, so in the interest
>> of seeing your changes go in, I'd recommend making things easier on us
>> mere mortals. At the very least, separate your doc changes out from your
>> code changes.
>>
>> Sincerely,
>> Someone who would like these changes or something like them to be applied
>
> Any updates here? It would be great if these changes could go in, but
> they would need to be broken down into much smaller chunks for that to
> happen.
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.
next prev parent reply other threads:[~2021-09-20 1:20 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 [this message]
2021-09-20 7:12 ` Stefan Kangas
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=875yuwujns.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=49065@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=fgunbin@fastmail.fm \
--cc=stefan@marxist.se \
/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).