From: immerrr again <immerrr@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>,
17862@debbugs.gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#17862: 24.3; regexp-opt docstring is incorrect
Date: Fri, 2 Sep 2016 15:30:34 +0300 [thread overview]
Message-ID: <CAERznn9Nt2+FbH10HEsAi1nqPjf3DQpyO3t3=-NM74PfcBde1Q@mail.gmail.com> (raw)
In-Reply-To: <83poomeqc5.fsf@gnu.org>
> Oh, the changelog entry text should be a sentence (capitalized, end with
> a period). And I guess you could combine the 2 changelog entries into
> 1
Attaching the fixed patch.
On Fri, Sep 2, 2016 at 10:03 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> His assignment is on file.
My existing assignment is accompanied by a disclaimer from my past
employer. I'm now self-employed, so probably a new disclaimer might be
in order, however AFAICS the long-term contract I'm fulfilling right
now has no clauses concerning the rights to the code I write. I might
need to bring this question to copyright assignment clerk.
next prev parent reply other threads:[~2016-09-02 12:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 7:20 bug#17862: 24.3; regexp-opt docstring is incorrect immerrr again
2014-06-30 13:37 ` Stefan Monnier
2014-07-01 7:15 ` immerrr again
2014-07-01 6:52 ` Glenn Morris
2014-07-01 7:16 ` Andreas Schwab
2014-07-01 15:41 ` Glenn Morris
2014-07-01 16:22 ` Stefan Monnier
2016-02-07 10:51 ` immerrr again
2016-07-29 1:10 ` npostavs
2016-07-29 3:57 ` immerrr again
2016-07-30 13:28 ` npostavs
2016-08-21 12:47 ` Noam Postavsky
2016-08-25 13:21 ` immerrr again
2016-08-26 1:08 ` npostavs
2016-08-29 8:45 ` immerrr again
2016-09-02 3:06 ` npostavs
2016-09-02 7:03 ` Eli Zaretskii
2016-09-02 12:30 ` immerrr again [this message]
2016-09-02 12:31 ` immerrr again
2016-09-02 13:11 ` Eli Zaretskii
2016-09-03 20:11 ` Noam Postavsky
2016-09-04 2:36 ` Eli Zaretskii
2016-09-04 3:59 ` npostavs
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='CAERznn9Nt2+FbH10HEsAi1nqPjf3DQpyO3t3=-NM74PfcBde1Q@mail.gmail.com' \
--to=immerrr@gmail.com \
--cc=17862@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=schwab@suse.de \
/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.