From: Eli Zaretskii <eliz@gnu.org>
To: Dima Kogan <lists@dima.secretsauce.net>
Cc: emacs-devel@gnu.org
Subject: Re: Embedded modifiers in the regex engine
Date: Thu, 31 Mar 2016 19:28:28 +0300 [thread overview]
Message-ID: <83k2kivcgj.fsf@gnu.org> (raw)
In-Reply-To: <87lh51yo5c.fsf@secretsauce.net> (message from Dima Kogan on Tue, 29 Mar 2016 14:23:11 -0700)
> From: Dima Kogan <lists@dima.secretsauce.net>
> Cc: emacs-devel@gnu.org
> Date: Tue, 29 Mar 2016 14:23:11 -0700
>
> >> > Also, please provide log messages for the changes.
> >>
> >> What kind of log messages? Git logs? These are terse because this
> >> project seems to have strict guidelines, and other messages I see are
> >> generally very terse. What would you like?
> >
> > See CONTRIBUTE: they should be Git log messages in the ChangeLog
> > format.
>
> Can you please be more specific about what is missing in the patches I
> sent?
A commit log message, formatted similarly to this one:
Adapt filenotify-tests.el according latest tests
* test/lisp/filenotify-tests.el (file-notify-test02-events)
(file-notify-test04-file-validity, file-notify-test05-dir-validity):
Remove superfluous `read-event' calls.
(file-notify-test02-events): Expect different events under MS
Windows 7 and 10.
(file-notify-test04-file-validity): Move `file-notify-valid-p'
check up.
next prev parent reply other threads:[~2016-03-31 16:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 1:32 Embedded modifiers in the regex engine Dima Kogan
2016-02-25 6:11 ` John Wiegley
2016-02-25 21:05 ` Stefan Monnier
2016-02-25 16:15 ` Eli Zaretskii
2016-02-26 7:19 ` Dima Kogan
2016-02-26 9:08 ` Eli Zaretskii
2016-02-28 1:50 ` Dima Kogan
2016-02-28 16:00 ` Eli Zaretskii
2016-02-29 13:30 ` Richard Stallman
2016-03-01 0:49 ` Aurélien Aptel
2016-03-01 16:55 ` Richard Stallman
2016-03-09 0:34 ` Dima Kogan
2016-03-28 0:23 ` Dima Kogan
2016-03-28 15:28 ` Eli Zaretskii
2016-03-28 18:05 ` Dima Kogan
2016-03-28 18:24 ` Eli Zaretskii
2016-03-29 21:23 ` Dima Kogan
2016-03-31 16:28 ` Eli Zaretskii [this message]
2016-04-23 4:17 ` Dima Kogan
2016-04-23 7:48 ` Eli Zaretskii
2016-04-24 7:34 ` Dima Kogan
2016-03-28 16:09 ` 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
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=83k2kivcgj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lists@dima.secretsauce.net \
/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).