From: Eli Zaretskii <eliz@gnu.org>
To: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Cc: emacs-orgmode@gnu.org, brandelune@gmail.com, emacs-devel@gnu.org
Subject: Re: info URL « open at point » patch
Date: Wed, 27 Jun 2018 21:11:22 +0300 [thread overview]
Message-ID: <83tvpop0ad.fsf@gnu.org> (raw)
In-Reply-To: <AM6PR10MB19573F76F06D5DCC04FA507E84480@AM6PR10MB1957.EURPRD10.PROD.OUTLOOK.COM> (message from Vincent Belaïche on Wed, 27 Jun 2018 17:39:33 +0000)
> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> CC: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>, "brandelune@gmail.com"
> <brandelune@gmail.com>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Wed, 27 Jun 2018 17:39:33 +0000
>
> Concerning the patch, I understood that you agree with it provided that
> it is upgraded to mention the change in the etc/NEWS file. So I did that
> & pushed the change.
Actually, I expected to see the full changeset before it went in.
For the future, please try to follow the conventions in NEWS, and also
please provide ChangeLog-style entries in the commit log message
describing the places (functions, variables, etc.) where you make
changes. See CONTRIBUTE for more details. I fixed the NEWS entry,
but I cannot fix the log entry.
Thanks.
next prev parent reply other threads:[~2018-06-27 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 6:57 info URL « open at point » patch Vincent Belaïche
2018-06-24 14:31 ` Eli Zaretskii
2018-06-24 16:48 ` Vincent Belaïche
2018-06-24 16:49 ` Vincent Belaïche
2018-06-24 17:03 ` Eli Zaretskii
2018-06-24 18:21 ` Vincent Belaïche
2018-06-24 18:45 ` Eli Zaretskii
2018-06-24 20:34 ` Vincent Belaïche
2018-06-25 2:30 ` Eli Zaretskii
2018-06-26 5:19 ` Vincent Belaïche
2018-06-26 5:47 ` Vincent Belaïche
2018-06-26 14:34 ` Eli Zaretskii
2018-06-27 17:39 ` Vincent Belaïche
2018-06-27 18:11 ` Eli Zaretskii [this message]
2018-06-26 14:30 ` Eli Zaretskii
2018-06-24 14:46 ` Jean-Christophe Helary
2018-06-24 20:30 ` Vincent Belaïche
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tvpop0ad.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brandelune@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=vincent.b.1@hotmail.fr \
/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/org-mode.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).