From: Eli Zaretskii <eliz@gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: joseph@codesourcery.com, gcc-patches@gcc.gnu.org,
gdb-patches@sources.redhat.com
Subject: Re: needed-list fails in libiberty
Date: Sun, 26 Apr 2009 17:44:00 -0000 [thread overview]
Message-ID: <838wlnfgyo.fsf@gnu.org> (raw)
In-Reply-To: <m3hc0cs6f4.fsf@google.com>
> Cc: joseph@codesourcery.com, gcc-patches@gcc.gnu.org,
> gdb-patches@sources.redhat.com
> From: Ian Lance Taylor <iant@google.com>
> Date: Sat, 25 Apr 2009 15:41:03 -0700
>
> This patch has already been approved
Thanks!
> but I gather that Eli does not have write access to the repository.
That's right.
next prev parent reply other threads:[~2009-04-26 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 14:10 Eli Zaretskii
2009-04-14 14:19 ` Joseph S. Myers
2009-04-14 14:42 ` Eli Zaretskii
2009-04-15 0:30 ` Ian Lance Taylor
2009-04-15 8:15 ` Eli Zaretskii
2009-04-15 13:50 ` Ian Lance Taylor
2009-04-16 17:47 ` Eli Zaretskii
2009-04-25 9:58 ` Eli Zaretskii
2009-04-25 22:41 ` Ian Lance Taylor
2009-04-26 17:44 ` Eli Zaretskii [this message]
2009-04-26 2:23 ` DJ Delorie
2009-04-26 17:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-04-14 14:10 Eli Zaretskii
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=838wlnfgyo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=iant@google.com \
--cc=joseph@codesourcery.com \
/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