From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: RFC: Adding BBDB to Emacs core
Date: Tue, 24 Apr 2018 21:50:02 -0400 [thread overview]
Message-ID: <jwvlgdcxdkb.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 65ee99c7-6c45-e477-d34b-8efb1aa4712d@cs.ucla.edu
> It's a tradeoff, though, as the runtime logic makes the code harder to
> maintain and (particularly) to test, and at some point it becomes more
> trouble than it's worth. This is why Gnus dropped support for Emacs
> 22 a couple of years ago. Even if ELPA packages should work on current and
> previous Emacs versions, today I would think that they shouldn't have to
> worry about porting to Emacs 23 or earlier, and that a package's maintainer
> can determine whether the cutoff is 22, 23, or even 24.
Of course, but that doesn't mean there needs to be several different
supported versions of the package. It just means you drop support for
old versions, as is the case in all packages. Nothing new here: no need
for different branches in elpa.git to go along with branches in
emacs.git just because of that.
Stefan
next prev parent reply other threads:[~2018-04-25 1:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 5:54 RFC: Adding BBDB to Emacs core Thomas Fitzsimmons
2018-04-14 12:24 ` Joshua Branson
2018-04-14 22:06 ` Eric Abrahamsen
2018-04-14 22:46 ` Joshua Branson
2018-04-15 6:18 ` Bozhidar Batsov
2018-04-16 5:21 ` John Wiegley
2018-04-16 14:53 ` Thomas Fitzsimmons
2018-04-16 18:36 ` Stefan Monnier
2018-04-16 20:30 ` Eric Abrahamsen
2018-04-17 3:37 ` Thomas Fitzsimmons
2018-04-23 12:53 ` Phillip Lord
2018-04-23 13:21 ` Stefan Monnier
2018-04-23 16:21 ` Phillip Lord
2018-04-23 17:45 ` Stefan Monnier
2018-04-24 21:41 ` Phillip Lord
2018-04-24 22:31 ` Stefan Monnier
2018-04-25 0:42 ` Paul Eggert
2018-04-25 1:50 ` Stefan Monnier [this message]
2018-04-25 9:21 ` Phillip Lord
2018-04-25 12:02 ` Stefan Monnier
2018-04-25 16:31 ` Phillip Lord
2018-04-25 16:57 ` Stefan Monnier
2018-04-26 14:59 ` Phillip Lord
2018-04-25 9:19 ` Phillip Lord
2018-04-25 16:04 ` Radon Rosborough
2018-04-25 16:32 ` Phillip Lord
2018-04-25 16:55 ` Stefan Monnier
2018-04-25 20:16 ` Radon Rosborough
2018-04-26 15:02 ` Phillip Lord
2018-04-26 16:38 ` Stefan Monnier
2018-04-27 9:57 ` Phillip Lord
2018-04-27 13:32 ` Stefan Monnier
2018-04-17 3:23 ` Roland Winkler
2018-04-17 4:56 ` John Wiegley
2018-04-17 13:07 ` Stefan Monnier
2018-04-17 15:13 ` Roland Winkler
2018-04-18 23:11 ` Stephen Leake
2018-04-23 12:57 ` Phillip Lord
2018-04-23 13:26 ` Stefan Monnier
2018-04-23 15:29 ` Roland Winkler
2018-04-14 22:13 ` Thomas Fitzsimmons
2018-04-14 13:34 ` Glenn Morris
2018-04-14 17:10 ` Radon Rosborough
2018-04-14 17:38 ` Thomas Fitzsimmons
2018-04-15 21:20 ` Phillip Lord
2018-04-16 3:11 ` Michael Welsh Duggan
2018-04-16 12:30 ` Stefan Monnier
2018-04-16 17:09 ` Achim Gratz
2018-04-16 18:10 ` Eli Zaretskii
2018-04-16 18:14 ` Achim Gratz
2018-04-23 12:45 ` Phillip Lord
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=jwvlgdcxdkb.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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.
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).