public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "gnu_andrew at member dot fsf dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug classpath/21869] We should to use StringBuilder instead of StringBuffer where appropriate.
Date: Wed, 07 May 2008 18:02:00 -0000	[thread overview]
Message-ID: <20080507180215.20641.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21869-7151@http.gcc.gnu.org/bugzilla/>



------- Comment #30 from gnu_andrew at member dot fsf dot org  2008-05-07 18:02 -------
Created an attachment (id=15602)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15602&action=view)
Move towards a CPStringBuilder-using code base


-- 


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


  parent reply	other threads:[~2008-05-07 18:02 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21869-7151@http.gcc.gnu.org/bugzilla/>
2007-10-09 18:42 ` gnu_andrew at member dot fsf dot org
2008-02-07 12:10 ` ian dot rogers at manchester dot ac dot uk
2008-02-17 15:58 ` gnu_andrew at member dot fsf dot org
2008-02-17 15:58 ` gnu_andrew at member dot fsf dot org
2008-02-17 15:58 ` gnu_andrew at member dot fsf dot org
2008-02-27 23:00 ` gnu_andrew at member dot fsf dot org
2008-03-01  9:14 ` gnu_andrew at member dot fsf dot org
2008-03-05 21:03 ` gnu_andrew at member dot fsf dot org
2008-03-05 21:03 ` gnu_andrew at member dot fsf dot org
2008-03-05 21:04 ` gnu_andrew at member dot fsf dot org
2008-03-05 21:04 ` gnu_andrew at member dot fsf dot org
2008-03-16 22:29 ` gnu_andrew at member dot fsf dot org
2008-03-16 22:45 ` gnu_andrew at member dot fsf dot org
2008-03-16 23:37 ` gnu_andrew at member dot fsf dot org
2008-03-17  0:37 ` gnu_andrew at member dot fsf dot org
2008-03-17  1:30 ` gnu_andrew at member dot fsf dot org
2008-04-27 22:01 ` gnu_andrew at member dot fsf dot org
2008-05-01  0:44 ` gnu_andrew at member dot fsf dot org
2008-05-01  0:44 ` gnu_andrew at member dot fsf dot org
2008-05-01  0:45 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:54 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:55 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:56 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:56 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:57 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:57 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:58 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:58 ` gnu_andrew at member dot fsf dot org
2008-05-07 17:59 ` ddaney at avtrex dot com
2008-05-07 18:01 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:02 ` gnu_andrew at member dot fsf dot org [this message]
2008-05-07 18:02 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:03 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:04 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:04 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:07 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:07 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:08 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:08 ` gnu_andrew at member dot fsf dot org
2008-05-07 18:10 ` gnu_andrew at member dot fsf dot org
2005-06-01 23:24 [Bug libgcj/21869] New: " daney at gcc dot gnu dot org
2005-07-27 17:39 ` [Bug classpath/21869] " 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=20080507180215.20641.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).