Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, dj@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: libiberty configuration for DJGPP
Date: Tue, 14 Apr 2009 14:33:00 -0000	[thread overview]
Message-ID: <83skkbmhk6.fsf@gnu.org> (raw)
In-Reply-To: <m3eivv5n8e.fsf@google.com>

> Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, DJ Delorie <dj@redhat.com>,
>         gdb-patches@sources.redhat.com
> From: Ian Lance Taylor <iant@google.com>
> Date: Tue, 14 Apr 2009 07:22:25 -0700
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 2009-04-14  Eli Zaretskii  <eliz@gnu.org>
> >
> > 	* configure.ac  (setobjs, msdosdjgpp): Move a-priori setting of
> > 	existing and required library functions to with_target_subdir
> > 	section, so that the native build does detect them at configure
> > 	time.
> 
> This is OK.

Is sources.redhat.com:/cvs/src the master repository for this file?
If not, I'm not sure I have write access to commit these changes.

> In the future, please send patches only to gcc-patches@, not to both
> gcc-patches@ and gcc@.  Thanks.

Will do, and sorry for the extra noise.

Thanks.


  reply	other threads:[~2009-04-14 14:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 13:30 Eli Zaretskii
2009-04-14 14:24 ` Ian Lance Taylor
2009-04-14 14:33   ` Eli Zaretskii [this message]
2009-04-14 14:56     ` Ian Lance Taylor
2009-04-14 15:45       ` Eli Zaretskii
2009-04-14 15:45       ` [RFC] change sources.redhat.com to sourceware.org in gdbadmin/ss dir (was: libiberty configuration for DJGPP) Pierre Muller
2009-04-14 16:06         ` Joel Brobecker
2009-04-14 18:26           ` Pierre Muller
2009-04-14 16:25       ` Pierre Muller
2009-04-14 19:21         ` Christopher Faylor
2009-04-14 17:46       ` libiberty configuration for DJGPP DJ Delorie
2009-04-14 17:58         ` 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=83skkbmhk6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=iant@google.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