From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 28867@debbugs.gnu.org
Subject: bug#28867: Acknowledgement (Replace gnus-copy-sequence with copy-tree)
Date: Tue, 21 Nov 2017 17:29:29 -0800 [thread overview]
Message-ID: <87zi7fnls6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k1zrfmd4.fsf@users.sourceforge.net> (Noam Postavsky's message of "Thu, 19 Oct 2017 06:44:23 -0400")
On 10/19/17 06:44 AM, Noam Postavsky wrote:
> tags 28867 + patch
> tags 28856 + patch
> quit
>
> Both patches look fine, the only possibly problem I can see is if some
> other packge relies on the gnus functions you are removing. Probably
> not an issue, since they're so trivially replaced by builtins anyway.
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> tags 28867 patch
>
> You have to send this to control@debbugs.gnu.org (which I've Bcc'd on
> this email).
What I'd like to do with this and also bug #28856 (regarding
gnus-last-element) is to leave the function definitions in place,
obsolete them, and remove all the calls.
I alerted one third-party package that was using gnus-last-element to
the impending change, and haven't found any others, but it seems like
obsoleting the functions is still safer.
I'll do that tomorrow, unless anyone objects.
prev parent reply other threads:[~2017-11-22 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 16:58 bug#28867: Replace gnus-copy-sequence with copy-tree Eric Abrahamsen
[not found] ` <handler.28867.B.150817319123733.ack@debbugs.gnu.org>
2017-10-16 17:02 ` bug#28867: Acknowledgement (Replace gnus-copy-sequence with copy-tree) Eric Abrahamsen
2017-10-19 10:44 ` Noam Postavsky
2017-10-19 15:05 ` Eric Abrahamsen
2017-10-19 15:10 ` Eric Abrahamsen
2017-11-22 1:29 ` Eric Abrahamsen [this message]
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=87zi7fnls6.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=28867@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.