all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: Bug #29083: Is it OK to add a new function to the emacs-26 branch?
Date: Wed, 01 Nov 2017 12:56:00 -0700	[thread overview]
Message-ID: <m2k1z9rcxb.fsf@newartisans.com> (raw)
In-Reply-To: <834lqdss2f.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Nov 2017 21:43:36 +0200")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

AM> However, the OP has requested that a function which actually displays this
AM> name be put into CC Mode. Would it still be OK to do this on the emacs-26
AM> branch, or is this branch now closed for such things?
>> 
>> I think that since we're now prepping for release with pretests out there,
>> it's become too late. Nothing stops us from getting a 26.2 out the door soon
>> after, though.

> That's true, but OTOH a new function that doesn't affect anything (because
> it isn't called from any place) cannot do much harm. So I tend to allow this
> exception.

If you're good with such an addition, Eli, then I'm OK with it too.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



  reply	other threads:[~2017-11-01 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 11:21 Bug #29083: Is it OK to add a new function to the emacs-26 branch? Alan Mackenzie
2017-11-01 13:27 ` Compro Prasad
2017-11-01 17:05 ` John Wiegley
2017-11-01 19:43   ` Eli Zaretskii
2017-11-01 19:56     ` John Wiegley [this message]
2017-11-02 19:24       ` Alan Mackenzie
2017-11-03 15:35 ` Stefan Monnier
2017-11-03 16:22   ` Alan Mackenzie
2017-11-03 17:04     ` Stefan Monnier

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=m2k1z9rcxb.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --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.