From: CHENG Gao <chenggao@royau.me>
To: emacs-devel@gnu.org
Subject: Re: Handling bugs in obsolete code
Date: Thu, 07 Jan 2016 16:28:23 +0800 [thread overview]
Message-ID: <m2ziwh3iag.fsf@royau.me> (raw)
In-Reply-To: ba8ohvmzf.fsf@fencepost.gnu.org
Many files were put into obsolete/ dir for long time, since 22.1 or
23.1. It does not make sense to continue keeping them there. But it's
just MPO.
How about some policy to handle this? Say keep version-1 or version-2.
For one last time, keep them all in 25.1 release tarball, and then
delete all except "Obsolete-since: 25.1/24.5", and then roll like this.
If anyone needs, they can pull from 25.1 tarball.
And maybe add instruction to each file, something like superceded-by
etc.
next prev parent reply other threads:[~2016-01-07 8:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:53 bug#1452: 23.0.60; Problem with nextstep, longlines-mode, Harald Hanche-Olsen
[not found] ` <handler.1452.B.122796683914175.ack@emacsbugs.donarmstrong.com>
2008-11-29 14:52 ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Harald Hanche-Olsen
2008-11-29 15:11 ` Harald Hanche-Olsen
2016-01-05 4:10 ` Andrew Hyatt
2016-01-05 17:32 ` Glenn Morris
2016-01-05 17:39 ` Andrew Hyatt
2016-01-05 17:53 ` Harald Hanche-Olsen
2016-01-05 18:38 ` Eli Zaretskii
2016-01-05 18:29 ` Eli Zaretskii
2016-01-05 20:38 ` John Wiegley
2016-01-05 20:46 ` Eli Zaretskii
2016-01-05 21:15 ` Harald Hanche-Olsen
2016-01-05 21:12 ` Andrew Hyatt
2016-01-05 21:34 ` John Wiegley
2016-01-05 21:50 ` Dmitry Gutov
2016-01-06 1:47 ` Andrew Hyatt
2016-01-06 1:53 ` Dmitry Gutov
2016-01-06 3:45 ` Eli Zaretskii
2016-01-07 1:42 ` Andrew Hyatt
2016-01-07 1:58 ` Handling bugs in obsolete code (was: bug#1452: ...) John Wiegley
2016-01-07 3:27 ` Handling bugs in obsolete code Andrew Hyatt
2016-01-07 6:03 ` John Wiegley
2016-01-07 7:59 ` Glenn Morris
2016-01-07 8:28 ` CHENG Gao [this message]
2016-01-07 16:10 ` Eli Zaretskii
2016-01-07 18:17 ` John Wiegley
2016-01-07 3:42 ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Eli Zaretskii
2016-01-07 3:54 ` Andrew Hyatt
2016-01-07 16:02 ` Eli Zaretskii
2016-01-06 8:28 ` Xue Fuqiao
2016-01-06 18:16 ` Glenn Morris
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=m2ziwh3iag.fsf@royau.me \
--to=chenggao@royau.me \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.