From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "roland@gnu.org" <roland@gnu.org>,
"occitan@esperanto.org" <occitan@esperanto.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: RE: compile.el ant error regexp does not match on MSW
Date: Sun, 4 Oct 2015 08:22:19 +0200 [thread overview]
Message-ID: <DUB109-W26A5D63F421344BAED851784490@phx.gbl> (raw)
In-Reply-To: <83io6n3jg7.fsf@gnu.org>
Thanks. I did it.
Vincent.
----------------------------------------
> Date: Sat, 3 Oct 2015 21:17:44 +0300
> From: eliz@gnu.org
> Subject: Re: compile.el ant error regexp does not match on MSW
> To: vincent.b.1@hotmail.fr
> CC: roland@gnu.org; occitan@esperanto.org; emacs-devel@gnu.org
>
>> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
>> Date: Sat, 3 Oct 2015 20:05:01 +0200
>> Cc: "roland@gnu.org" <roland@gnu.org>,
>> "occitan@esperanto.org" <occitan@esperanto.org>,
>> emacs-devel <emacs-devel@gnu.org>
>>
>> Just for my clarification, when you write: "Please do write ChangeLog entries", you mean writing a commit comment (git commit -m "<my comment>") in the same format as for a ChangeLog entry, and then this can be used to generate the ChangeLog file.
>
> Yes.
>
> This is all explained in much more detail in the file CONTRIBUTE which
> you will find in the cloned repository.
>
>
next prev parent reply other threads:[~2015-10-04 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 16:29 compile.el ant error regexp does not match on MSW Vincent Belaïche
2015-10-03 17:07 ` Eli Zaretskii
2015-10-03 18:05 ` Vincent Belaïche
2015-10-03 18:17 ` Eli Zaretskii
2015-10-04 6:22 ` Vincent Belaïche [this message]
2015-10-04 10:31 ` what happened of the List-Id header? Francesco Potortì
2015-10-04 11:02 ` Eli Zaretskii
2015-10-04 11:09 ` Francesco Potortì
2015-10-04 11:11 ` Andreas Schwab
2015-10-04 11:33 ` Francesco Potortì
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=DUB109-W26A5D63F421344BAED851784490@phx.gbl \
--to=vincent.b.1@hotmail.fr \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=occitan@esperanto.org \
--cc=roland@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.