From: "Ludovic Courtès" <INVALID.NOREPLY@gnu.org>
To: ludo@gnu.org, wingo@pobox.com, jao@gnu.org, 9837@debbugs.gnu.org
Subject: bug#9837: [bug #30903] Error line numbers are wrong
Date: Sat, 22 Oct 2011 14:23:28 +0000 [thread overview]
Message-ID: <20111022-142328.sv15145.68879@savannah.gnu.org> (raw)
In-Reply-To: <20110202-194711.sv20118.10490@savannah.gnu.org>
Update of bug #30903 (project guile):
Status: None => Wont Fix
Open/Closed: Open => Closed
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30903>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2011-10-22 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 2:08 [bug #30903] Error line numbers are wrong Jose Antonio Ortega Ruiz
2010-08-30 2:13 ` Jose Antonio Ortega Ruiz
2011-02-02 19:47 ` Andy Wingo
2011-10-22 14:23 ` Ludovic Courtès [this message]
2011-10-22 15:59 ` bug#9837: " Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111022-142328.sv15145.68879@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=9837@debbugs.gnu.org \
--cc=jao@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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.
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).