From: Jay Belanger <jay.p.belanger@gmail.com>
To: raman <raman@google.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
sxemacs-devel@sxemacs.org, ding@gnus.org
Subject: Re: Moving Gnus development to Emacs?
Date: Wed, 30 Dec 2015 13:05:00 -0600 [thread overview]
Message-ID: <87ege3sqoz.fsf@gmail.com> (raw)
In-Reply-To: <p91bn973nhm.fsf@google.com> (raman@google.com's message of "Wed, 30 Dec 2015 08:33:25 -0800")
raman <raman@google.com> writes:
...
> This would be nice!> (Excuse the crossposting.)
Why?
>> So: I want to know how all y'all would feel if I closed git.gnus.org and
>> started bringing the Gnus code base in the Emacs trunk up to modern
>> Emacs standards. That would mean removing basically all compat code.
These are three different issues, right?
Not including new compat code is one thing, but why remove what is
already there?
How is the Gnus code base not up to modern standards? Why would
bring it up to snuff require removing compat code?
And these two issues can be dealt with regardless of where the Gnus
development occurs; moving it to the Emacs trunk means only people
running git Emacs can use/work on the latest Gnus.
next prev parent reply other threads:[~2015-12-30 19:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 11:43 Lars Magne Ingebrigtsen
[not found] ` <mailman.1827.1451475821.29210.sxemacs-devel-sxemacs.org@lists.sxemacs.org>
2015-12-30 14:33 ` Moving Gnus development to Emacs Steve Youngs
2015-12-30 15:15 ` Ivan Shmakov
2016-01-01 19:21 ` Steinar Bang
2016-01-02 3:28 ` Lars Magne Ingebrigtsen
2015-12-30 16:33 ` Moving Gnus development to Emacs? raman
2015-12-30 19:05 ` Jay Belanger [this message]
2015-12-30 19:25 ` Nikolaus Rath
2015-12-31 17:40 ` Lars Magne Ingebrigtsen
2015-12-31 18:35 ` Benjamin Slade
2015-12-30 18:44 ` John Wiegley
2015-12-31 0:46 ` Katsumi Yamaoka
2015-12-31 13:50 ` Eli Zaretskii
2015-12-31 9:18 ` Julien Danjou
2015-12-31 9:40 ` David Engster
2015-12-31 11:43 ` Michael Albinus
2015-12-31 12:29 ` CHENG Gao
2015-12-31 14:35 ` Xue Fuqiao
2015-12-31 14:52 ` CHENG Gao
2016-01-01 0:10 ` Xue Fuqiao
2016-01-01 7:02 ` CHENG Gao
2015-12-31 17:10 ` Lars Magne Ingebrigtsen
2015-12-31 17:15 ` Adam Sjøgren
2016-01-02 17:39 ` Lars Magne Ingebrigtsen
2016-01-02 20:31 ` Steinar Bang
2016-01-03 18:24 ` Bill Wohler
2016-01-04 0:48 ` Lars Magne Ingebrigtsen
2016-01-04 1:05 ` John Wiegley
2016-01-04 3:47 ` Steve Youngs
2016-01-06 7:18 ` Lars Magne Ingebrigtsen
2016-01-06 7:38 ` CHENG Gao
2016-01-06 8:50 ` Andreas Schwab
2016-01-25 15:07 ` Ted Zlatanov
2016-01-28 12:45 ` Greg Troxel
2015-12-31 10:15 ` Eric Abrahamsen
2015-12-31 17:43 ` Lars Magne Ingebrigtsen
2016-01-01 21:43 ` Göktuğ Kayaalp
2015-12-31 17:04 ` Uwe Brauer
2016-01-18 7:26 gnus-summary-refer-parent-article bug Dave Abrahams
2016-01-18 12:43 ` Alan Schmitt
2016-01-18 15:47 ` Dave Abrahams
2016-01-19 0:25 ` Katsumi Yamaoka
2016-01-19 15:59 ` Dave Abrahams
2016-01-19 22:10 ` Katsumi Yamaoka
2016-01-20 11:04 ` Alan Schmitt
2016-01-20 23:04 ` Katsumi Yamaoka
2016-01-21 10:21 ` Alan Schmitt
2016-01-22 2:37 ` Moving Gnus development to Emacs? Katsumi Yamaoka
2016-01-22 7:53 ` Alan Schmitt
2016-01-22 9:45 ` Katsumi Yamaoka
2016-01-22 11:28 ` Michael Albinus
2016-01-24 23:35 ` Katsumi Yamaoka
2016-01-25 1:58 ` Mike Kupfer
2016-01-25 3:11 ` Katsumi Yamaoka
2016-01-25 13:12 ` Alan Schmitt
2016-01-22 12:25 ` Alan Schmitt
2016-01-25 1:37 ` Katsumi Yamaoka
2016-02-06 5:51 ` Lars Ingebrigtsen
2016-02-06 14:36 ` Adam Sjøgren
2016-02-06 14:38 ` Adam Sjøgren
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=87ege3sqoz.fsf@gmail.com \
--to=jay.p.belanger@gmail.com \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--cc=raman@google.com \
--cc=sxemacs-devel@sxemacs.org \
/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 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 NNTP newsgroup(s).