Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>,
	GCC Development <gcc@gcc.gnu.org>,	GDB <gdb@sourceware.org>
Subject: Re: RFC: Add zlib source to src CVS resposity
Date: Mon, 01 Nov 2010 17:19:00 -0000	[thread overview]
Message-ID: <20101101171919.GA32741@caradoc.them.org> (raw)
In-Reply-To: <4CCEF548.4000502@redhat.com>

On Mon, Nov 01, 2010 at 05:13:44PM +0000, Nick Clifton wrote:
> At the moment I feel that the pros outweigh the cons.  What do other
> people think ?

I was asked not to include expat in GDB, which was a similar
situation.  I don't remember if this was an FSF issue; I know that the
FSF, in general, dislikes duplicated source code in packages, but I
don't know if they care when the duplicated bits are non-GNU.  There
were definitely GDB developers that disliked bundling expat, so
perhaps you can find the reasons in the archives.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2010-11-01 17:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikYSxV51_452Wuqox6mQ3_QwNjzNkBgV=NzKk4f__16997.3676828251$1288473196$gmane$org@mail.gmail.com>
2010-10-30 21:37 ` Frank Ch. Eigler
2010-10-30 22:28   ` H.J. Lu
2010-10-31 18:42   ` Ian Lance Taylor
2010-10-31 18:58     ` H.J. Lu
2010-10-31 19:13       ` Ian Lance Taylor
2010-11-01 17:13         ` Nick Clifton
2010-11-01 17:19           ` Daniel Jacobowitz [this message]
2010-11-01 23:56           ` Alan Modra
2010-11-02  1:03             ` Christopher Faylor
2010-11-02  8:19               ` Nick Clifton
2010-11-02 13:22                 ` Ian Lance Taylor
2010-11-09 14:19                   ` Mike Frysinger
2010-11-02 10:46         ` Paolo Bonzini
2010-10-31 19:54     ` Weddington, Eric
2010-10-30 21:12 H.J. Lu

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=20101101171919.GA32741@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=nickc@redhat.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