From: Jan Stranik via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58847@debbugs.gnu.org
Subject: bug#58847: Patch to properly parse c++11 multiline strings
Date: Sat, 29 Oct 2022 09:57:35 -0400 [thread overview]
Message-ID: <CFB83328-1DF4-49C9-AE90-C3C34E5457D8@stranik.org> (raw)
In-Reply-To: <83fsf7hy6h.fsf@gnu.org>
Happy to fill paperwork to assign all rights for this patch.
Sent from my iPhone
> On Oct 29, 2022, at 3:43 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>
>>
>> Date: Fri, 28 Oct 2022 16:13:42 -0400
>> From: Jan Stranik via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> I’m happy user of emacs and ebrowse feature. Recently I noticed that ebrowse does not work for multi-line strings in c++.
>> The r-string parsing is on also for c files, but it does not matter since c does not have r strings.
>
> This patch is long enough for us to require that you assign the
> copyright for your code to the FSF. Would you be willing start your
> legal paperwork at this time, so that we could accept your
> contribution? If so, I will send you the form to fill and the
> instructions to email it.
>
> Thanks.
next prev parent reply other threads:[~2022-10-29 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 20:13 bug#58847: Patch to properly parse c++11 multiline strings Jan Stranik via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-29 7:41 ` Eli Zaretskii
2022-10-29 7:48 ` Gerd Möllmann
2022-10-29 7:43 ` Eli Zaretskii
2022-10-29 13:57 ` Jan Stranik via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-29 15:14 ` Eli Zaretskii
2022-11-17 4:28 ` Jan Stranik via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 6:58 ` Eli Zaretskii
2022-11-17 10:11 ` Eli Zaretskii
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=CFB83328-1DF4-49C9-AE90-C3C34E5457D8@stranik.org \
--to=bug-gnu-emacs@gnu.org \
--cc=58847@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jan@stranik.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.