From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Docstring of make-symbolic-link
Date: Thu, 13 Jun 2019 09:41:49 +0200 [thread overview]
Message-ID: <CAAeL0SSBzxDzCW0_d5q2UFV0idM2PJ9SY04Dhjpymaiw7sx99Q@mail.gmail.com> (raw)
In-Reply-To: <837e9q13yn.fsf@gnu.org>
> I understand that you prefer NEWNAME as well, so I'm in a minority
> here.
Not really. My comment was (or at least, intended to be, but my
English perhaps got in the middle) that I thought that using NEWNAME
was not the result of copy&paste, but a deliberate decision. But I
didn't really express any preference on my own.
> So now you know my views on this, and can make up your mind.
I'm partial to LINKNAME. I find it much more descriptive and to the
point that NEWNAME.
> But
> whatever you do, let's do that on master, as the first pretest of
> Emacs 26.3 is already out, and I'd prefer to release it VSN, if
> possible.
Fixing it to LINKNAME is just adjusting the docstring and one info
file, so it shouldn't be a problem. I thought documentation fixes and
typos are allowed during the pretest? Or do you really prefer even
that change to go to the master?
next prev parent reply other threads:[~2019-06-13 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 19:44 Docstring of make-symbolic-link Juanma Barranquero
2019-06-11 14:22 ` Eli Zaretskii
2019-06-11 15:50 ` Paul Eggert
2019-06-12 22:31 ` Juanma Barranquero
2019-06-13 4:53 ` Eli Zaretskii
2019-06-13 7:41 ` Juanma Barranquero [this message]
2019-06-13 8:57 ` Eli Zaretskii
2019-06-19 21:33 ` Juanma Barranquero
2019-06-21 7:52 ` Eli Zaretskii
2019-06-21 7:57 ` Juanma Barranquero
2019-06-21 8:24 ` Eli Zaretskii
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=CAAeL0SSBzxDzCW0_d5q2UFV0idM2PJ9SY04Dhjpymaiw7sx99Q@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eggert@cs.ucla.edu \
--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 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).