From: Andreas Stricker <astricker@futurelab.ch>
To: "Otto Kekäläinen" <otto@fsfe.org>
Cc: git@vger.kernel.org
Subject: Re: [bug-gettext] xgettext Javascript scanner bugfix and test suite improvements
Date: Wed, 24 Apr 2013 21:18:39 +0200 [thread overview]
Message-ID: <5178300F.7060900@futurelab.ch> (raw)
In-Reply-To: <CAHj_TLCKtXbuqCH-vE_Qy5QqNQi194C26VDG7QE3vjxVQkWrhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
Hi Otto
> I don't have skills to review the patch, but I just wanted to thank
> you for working on the JavaScript parser
Thank you :-)
> I've been hoping that somebody would fix it!
With fixing you mean getting it into the next release? Or do you
know of any other problems with it? I'm currently trying to find
all remaining show-stopping bugs, so if anyone knows one I'm
very happy to know about it.
Regards, Andy
[-- Attachment #2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 3531 bytes --]
parent reply other threads:[~2013-04-24 19:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAHj_TLCKtXbuqCH-vE_Qy5QqNQi194C26VDG7QE3vjxVQkWrhQ@mail.gmail.com>]
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=5178300F.7060900@futurelab.ch \
--to=astricker@futurelab.ch \
--cc=git@vger.kernel.org \
--cc=otto@fsfe.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.
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 NNTP newsgroup(s).