From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Cleaning up further compat code
Date: Mon, 04 Apr 2016 20:13:41 +0200 [thread overview]
Message-ID: <m3r3elnsx6.fsf@gnus.org> (raw)
In-Reply-To: <jwvinzx1rx3.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 04 Apr 2016 08:35:58 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> No, please don't. If you want to keep that data, keep it in the
> affected files, not in a separate file.
>
> How 'bout a pseudo-header like
>
> Should-work-in: Emacs-trunk
>
> This way it can also be used for other cases such as
>
> Should-work-in: XEmacs
>
> or
>
> Should-work-in: Emacs≥23
I like it, but I assumed that was off the table, since these files are
maintained outside Emacs. :-) If we can do janitorial changes to files
to clarify that we shouldn't do janitorial changes in them, then things
get easier to handle.
> For multifile packages, we could put that pseudo-header only in the
> main file.
Well... then this no longer can be automated. I'd really like to have
a mode line thing stating the maintainability status of the file when
doing cleanups...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-04 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 16:29 Cleaning up further compat code Lars Magne Ingebrigtsen
2016-04-03 16:33 ` Lars Magne Ingebrigtsen
2016-04-03 19:09 ` Lars Magne Ingebrigtsen
2016-04-03 23:21 ` John Wiegley
2016-04-03 16:54 ` Michael Albinus
2016-04-04 7:06 ` Lars Magne Ingebrigtsen
2016-04-04 7:31 ` Michael Albinus
2016-04-04 7:56 ` Lars Magne Ingebrigtsen
2016-04-04 12:35 ` Stefan Monnier
2016-04-04 15:04 ` Eli Zaretskii
2016-04-04 18:13 ` Lars Magne Ingebrigtsen [this message]
2016-04-05 0:20 ` Stefan Monnier
2016-04-06 11:30 ` Lars Magne Ingebrigtsen
2016-04-05 0:16 ` Xue Fuqiao
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=m3r3elnsx6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).