From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: eggert@cs.ucla.edu, ohwoeowho@gmail.com, emacs-devel@gnu.org
Subject: Re: Is it time to remove INTERNAL_FIELD?
Date: Sat, 25 Apr 2015 17:41:33 +0300 [thread overview]
Message-ID: <83k2x0xobm.fsf@gnu.org> (raw)
In-Reply-To: <jwvd22se12u.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Oleh Krehel <ohwoeowho@gmail.com>, eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Sat, 25 Apr 2015 10:28:02 -0400
>
> > I'd like to know as well. So far no one objected to leaving the
> > trailing underscores for the sake of the concurrency branch. So
> > unless someone does come up with objections soon, I'd interpret that
> > as meaning that BVAR and KVAR should still append the underscore, and
> > the fields marked INTERNAL till today should have that underscore.
>
> I'm not opposed to removing INTERNAL_FIELD and wouldn't oppose removing
> the underscore either. But if Eli wants to keep either of them that's
> fine by me as well.
Unless the concurrency branch is officially and finally dead, I'd like
to keep the underscores, to make it easier to revive that branch, if
and when some volunteer emerges.
> The only problem I have with this is the fact that we're just going
> back&forth on this.
We didn't yet get back on this, except in the
scratch/remove-internal-field branch.
next prev parent reply other threads:[~2015-04-25 14:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 9:55 Is it time to remove INTERNAL_FIELD? Oleh Krehel
2015-04-23 10:08 ` Paul Eggert
2015-04-23 10:10 ` Oleh Krehel
2015-04-23 10:17 ` Paul Eggert
2015-04-23 10:56 ` Eli Zaretskii
2015-04-23 10:56 ` Oleh Krehel
2015-04-23 11:17 ` Eli Zaretskii
2015-04-23 11:32 ` Oleh Krehel
2015-04-23 12:01 ` Eli Zaretskii
2015-04-23 12:05 ` Oleh Krehel
2015-04-23 12:37 ` Eli Zaretskii
2015-04-25 10:57 ` Oleh Krehel
2015-04-25 11:28 ` Eli Zaretskii
2015-04-25 14:28 ` Stefan Monnier
2015-04-25 14:41 ` Eli Zaretskii [this message]
2015-04-28 7:39 ` Oleh Krehel
2015-04-28 13:20 ` Stefan Monnier
2015-04-28 15:07 ` Eli Zaretskii
2015-04-28 15:11 ` Oleh Krehel
2015-04-28 15:23 ` Eli Zaretskii
2015-04-28 18:58 ` Oleh Krehel
2015-04-28 19:21 ` Eli Zaretskii
2015-04-23 11:00 ` Eli Zaretskii
2015-04-23 13:24 ` Stefan Monnier
2015-04-23 13:30 ` Oleh Krehel
2015-04-23 13:53 ` Eli Zaretskii
2015-04-23 14:07 ` Oleh Krehel
2015-04-23 14:50 ` Nicolas Richard
2015-04-23 15:34 ` Eli Zaretskii
2015-04-24 10:44 ` Nicolas Richard
2015-04-23 15:29 ` Eli Zaretskii
2015-04-23 16:32 ` Oleh Krehel
2015-04-23 17:00 ` Eli Zaretskii
2015-04-23 17:09 ` Oleh Krehel
2015-04-23 17:29 ` Eli Zaretskii
2015-04-23 17:14 ` Stefan Monnier
2015-04-23 17:31 ` Eli Zaretskii
2015-04-23 13:30 ` Stefan Monnier
2015-04-23 13:33 ` Oleh Krehel
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=83k2x0xobm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=ohwoeowho@gmail.com \
/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).