Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, gdb@sourceware.org
Subject: Re: gdb 7.0: 5 weeks to branch-time...
Date: Fri, 03 Apr 2009 03:37:00 -0000	[thread overview]
Message-ID: <20090403033749.GA14966@caradoc.them.org> (raw)
In-Reply-To: <uskkqj175.fsf@gnu.org>

On Thu, Apr 02, 2009 at 10:38:22PM +0300, Eli Zaretskii wrote:
> > Date: Thu, 2 Apr 2009 11:11:37 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
> > 
> > On Thu, Apr 02, 2009 at 06:24:14AM +0300, Eli Zaretskii wrote:
> > > I still have the issues with file names reported here:
> > > 
> > >   http://sourceware.org/ml/gdb-patches/2009-03/msg00618.html
> > > 
> > > I take it that the silence means everyone agrees with the renaming?
> > > If so, I will give it a go in a day or two.
> > 
> > We import these files from gnulib.  Any time we import them, they'll
> > get the same names.
> 
> Can't the import script rename them?

The import script comes from gnulib...

> > Maybe you could raise this problem with the gnulib developers?
> 
> I don't think I stand a chance, unless GDB as a project will ask for
> that.

I can't see why not.  You're an interested developer in your own right.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-04-03  3:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 21:58 Joel Brobecker
2009-04-01 22:14 ` Tom Tromey
2009-04-02 15:05   ` Thiago Jung Bauermann
2009-04-02 17:31   ` Joel Brobecker
2009-04-02 17:36     ` Tom Tromey
2009-04-02  3:26 ` Eli Zaretskii
2009-04-02 15:11   ` Daniel Jacobowitz
2009-04-02 19:38     ` Eli Zaretskii
2009-04-03  3:37       ` Daniel Jacobowitz [this message]
2009-04-03 11:42         ` Eli Zaretskii
2009-04-02 15:29 ` Thiago Jung Bauermann
2009-04-02 15:40   ` Joel Brobecker
2009-04-02 17:50 ` Pedro Alves

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=20090403033749.GA14966@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.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