From: Diego Novillo <dnovillo@google.com>
To: Rafael Espindola <espindola@google.com>
Cc: Leandro Nini <drfiemost@email.it>, gcc@gcc.gnu.org
Subject: Re: Possible endless loop in lto-wrapper
Date: Mon, 23 Nov 2009 19:03:00 -0000 [thread overview]
Message-ID: <b798aad50911231103l7be8752an5e8af954c12a5aa3@mail.gmail.com> (raw)
In-Reply-To: <38a0d8450911231059t29d1aa81u72072b5f52ae93c@mail.gmail.com>
On Mon, Nov 23, 2009 at 13:59, Rafael Espindola <espindola@google.com> wrote:
> 2009-11-23 Rafael Avila de Espindola <espindola@google.com>
>
> * lto-wrapper.c (lto_wrapper_exit): Don't try to delete files if
> being called recursively.
OK.
Diego.
next prev parent reply other threads:[~2009-11-23 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 8:54 Leandro Nini
2009-11-23 19:00 ` Rafael Espindola
2009-11-23 19:03 ` Diego Novillo [this message]
[not found] <331707e8286fe9d5b7d3b5f0c83db4a7@213.92.108.204>
2009-11-24 15:01 ` Rafael Espindola
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=b798aad50911231103l7be8752an5e8af954c12a5aa3@mail.gmail.com \
--to=dnovillo@google.com \
--cc=drfiemost@email.it \
--cc=espindola@google.com \
--cc=gcc@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).