public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "konqueror at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/26202] Regex bug "++"
Date: Fri, 10 Feb 2006 08:29:00 -0000	[thread overview]
Message-ID: <20060210082919.22463.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26202-83@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from konqueror at gmx dot de  2006-02-10 08:29 -------
Subject: Re:   New: Regex bug "++"

Works fine with jamvm 1.4.2 and current GNU classpath CVS.
Porting this fix to 4.1 branchshould be done.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26202


  reply	other threads:[~2006-02-10  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 23:21 [Bug libgcj/26202] New: " green at redhat dot com
2006-02-10  8:29 ` konqueror at gmx dot de [this message]
2006-02-10 19:52 ` [Bug libgcj/26202] " tromey at gcc dot gnu dot org
2006-02-10 19:54 ` tromey at gcc dot gnu dot org

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=20060210082919.22463.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).