From: Eli Zaretskii <eliz@gnu.org>
To: Dieter Deyke <dieter.deyke@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] elpa/packages/sokoban/sokoban.el
Date: Sun, 09 Jul 2017 17:52:41 +0300 [thread overview]
Message-ID: <83h8ylk6h2.fsf@gnu.org> (raw)
In-Reply-To: <877ezhllwi.fsf@deyke2> (message from Dieter Deyke on Sun, 09 Jul 2017 16:34:05 +0200)
> From: Dieter Deyke <dieter.deyke@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 09 Jul 2017 16:34:05 +0200
>
> > Please show the commit log message you intend to use.
> >
> > Also, does this warrant a NEWS entry?
> >
> > Thanks.
>
> The commit log message I was about to use is
>
> change player and block color if on target
In general, commit log messages should follow the format of ChangeLog
files as described in CONTRIBUTE. But maybe this is not required for
ELPA? (I thought sokoban.el was bundled with Emacs, sorry for not
looking closer.)
> About a NEWS entry, I do not know. Does ELPA have a separate NEWS file?
No, I don't think so. Again, I missed the fact that sokoban.el is an
ELPA package.
Thanks.
next prev parent reply other threads:[~2017-07-09 14:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 13:36 [PATCH] elpa/packages/sokoban/sokoban.el Dieter Deyke
2017-07-09 14:15 ` Eli Zaretskii
2017-07-09 14:34 ` Dieter Deyke
2017-07-09 14:52 ` Eli Zaretskii [this message]
2017-07-11 15:17 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2017-07-16 14:14 Dieter Deyke
2017-07-16 16:01 ` Stefan Monnier
2017-07-16 16:57 ` Dieter Deyke
2017-07-25 11:36 Dieter Deyke
2017-07-25 14:24 ` Stefan Monnier
2019-02-07 10:51 Dieter Deyke
2019-02-07 12:53 ` Clément Pit-Claudel
2019-02-07 14:42 ` Eli Zaretskii
2019-02-07 15:57 ` Dieter Deyke
2019-02-07 16:08 ` Clément Pit-Claudel
2019-02-07 16:11 ` Dieter Deyke
2019-02-07 16:55 ` Andreas Schwab
2019-02-08 3:34 ` Stefan Monnier
2019-02-07 14:56 ` Stefan Monnier
2019-02-12 12:30 Dieter Deyke
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=83h8ylk6h2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dieter.deyke@gmail.com \
--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.