public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: msnyder@sonic.net
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
	        binutils@sourceware.org, ian@airs.com, bje@ibm.com,
	dj@redhat.com,         dberlin@dberlin.org
Subject: Re: PATCH: libiberty/make-relative-prefix.c, resource leak.
Date: Fri, 03 Aug 2007 16:32:00 -0000	[thread overview]
Message-ID: <m3ir7w7f87.fsf@localhost.localdomain> (raw)
In-Reply-To: <4387.12.7.175.2.1185931095.squirrel@webmail.sonic.net>

msnyder@sonic.net writes:

> 2007-07-31  Michael Snyder  <msnyder@access-company.com>
> 
> 	* make-relative-prefix.c (make_relative_prefix_1): Resource leak.

This is OK.

Please apply it to the gcc repository before the src repository.

Thanks.

Ian

      reply	other threads:[~2007-08-03 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  1:18 msnyder
2007-08-03 16:32 ` Ian Lance Taylor [this message]

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=m3ir7w7f87.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=bje@ibm.com \
    --cc=dberlin@dberlin.org \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ian@airs.com \
    --cc=msnyder@sonic.net \
    /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).