From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: 21496-done@debbugs.gnu.org, jostein@kjonigsen.net,
Jan Nieuwenhuizen <janneke@gnu.org>
Subject: bug#21496: 25.0.50; guile-file compilation-error regexp is too wide
Date: Sun, 20 Sep 2015 15:49:17 -0400 [thread overview]
Message-ID: <jwvio74oov7.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <1442773828.606107.388698793.69A96030@webmail.messagingengine.com> ("Jostein Kjønigsen"'s message of "Sun, 20 Sep 2015 20:30:28 +0200")
> See updated patch. It should address all concerns raised so far.
Indeed, thank you. Installed.
We should file a bug report with the Guile guys: they should better
follow the GNU Coding Standard in their error messages (i.e. use
<file>:<line> rather than having the file name on some earlier line).
> To my knowledge I have not filled in any FSF copyright assignment
> papers yet, so I assume that will be next on my list of tasks to
> complete. I proceed with that independently of this bug.
Great. For now I installed it as a "tiny change", but indeed if you
want to provide further changes, it's better to sign the paperwork.
> Stefan: Do you need to be kept on CC for that process, or is
> everything else OK?
You can put me on the Cc, but as long as things are working normally,
it's not needed.
Stefan
prev parent reply other threads:[~2015-09-20 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:14 bug#21496: 25.0.50; guile-file compilation-error regexp is too wide Jostein Kjønigsen
2015-09-16 21:52 ` Stefan Monnier
2015-09-16 22:00 ` Jostein Kjønigsen
2015-09-20 7:44 ` Jostein Kjønigsen
2015-09-20 7:59 ` Andreas Schwab
2015-09-20 8:08 ` Jostein Kjønigsen
2015-09-20 9:10 ` Jostein Kjønigsen
2015-09-20 15:20 ` Stefan Monnier
2015-09-20 18:30 ` Jostein Kjønigsen
2015-09-20 19:49 ` Stefan Monnier [this message]
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=jwvio74oov7.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=21496-done@debbugs.gnu.org \
--cc=janneke@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.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).