public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, roman.kagan@itep.ru, tromey@gcc.gnu.org Subject: Re: libgcj/4728: java.util.zip.GZIPOutputStream.write(int) doesn't update CRC Date: Mon, 29 Oct 2001 13:49:00 -0000 [thread overview] Message-ID: <20011029214958.24768.qmail@sourceware.cygnus.com> (raw) Synopsis: java.util.zip.GZIPOutputStream.write(int) doesn't update CRC Responsible-Changed-From-To: unassigned->tromey Responsible-Changed-By: tromey Responsible-Changed-When: Mon Oct 29 13:49:57 2001 Responsible-Changed-Why: I'm handling it. State-Changed-From-To: open->closed State-Changed-By: tromey State-Changed-When: Mon Oct 29 13:49:57 2001 State-Changed-Why: Thanks a lot for your report and analysis. I checked in the fix. It will appear in gcc 3.1. If it looks like 3.0.3 will be released (I don't know) then I think this patch should go in to it as well. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4728&database=gcc
next reply other threads:[~2001-10-29 13:49 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-29 13:49 tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-10-29 3:46 roman.kagan
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=20011029214958.24768.qmail@sourceware.cygnus.com \ --to=tromey@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=roman.kagan@itep.ru \ /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: linkBe 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).