public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Andreas Schwab <schwab@suse.de>,
	 gcc-patches@gcc.gnu.org, 	  libstdc++@gcc.gnu.org
Subject: Re: Make sure symbol version script is writeable
Date: Mon, 25 Jun 2007 18:50:00 -0000	[thread overview]
Message-ID: <m3vedbri1b.fsf@codesourcery.com> (raw)
In-Reply-To: <467D7D64.6020407@codesourcery.com> (Mark Mitchell's message of "Sat, 23 Jun 2007 14:07:00 -0600")


Mark Mitchell <mark@codesourcery.com> writes:
> It doesn't look like this patch was ever applied.  With the change
> Andreas has suggested, this is OK after the lockdown.

Thanks very much.  I'll wait for the end of the lockdown.

  reply	other threads:[~2007-06-25 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 21:11 Jim Blandy
2007-05-07 22:22 ` Andreas Schwab
2007-05-08  1:01   ` Jim Blandy
2007-06-23 20:27     ` Mark Mitchell
2007-06-25 18:50       ` Jim Blandy [this message]
2007-08-07 21:07       ` Jim Blandy

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=m3vedbri1b.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=schwab@suse.de \
    /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).