Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	gdb-patches@sourceware.org, 	Michael Snyder <msnyder@vmware.com>
Subject: Re: [RFC] what should we do about COPYING?
Date: Mon, 21 Dec 2009 07:55:00 -0000	[thread overview]
Message-ID: <20091221075520.GN2788@adacore.com> (raw)
In-Reply-To: <4B2E3440.7070609@codesourcery.com>

> Back then, simulators in GDB were still somewhat of a novel concept,
> and we waffled about whether to officially consider them part of
> GDB, or as a separate library that happened to be linked in - the
> simulator could always be built as its own program, and GDB could be
> built without simulator. Plus at the time we really really really
> wanted a PPC simulator. :-)

We still need the ppc simulator :) (although we have also started testing
the ppc-elf GDB over qemu, with good results too).

I don't see the rush in addressing this inconsistency with the rest
of GDB, but I have a feeling that this will need to be addressed at
some point. The argument that the sim is a library separate from GDB
might have held for the sim ppc (assuming it was published elsewhere),
but I am not sure it works for all sim implementations.

But for now, I will take a break from licensing issues :).

Thanks for the feedback!
-- 
Joel


      reply	other threads:[~2009-12-21  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  7:33 Joel Brobecker
2009-12-18 15:52 ` Stan Shebs
2009-12-18 17:36 ` Michael Snyder
2009-12-18 17:43   ` Pedro Alves
2009-12-20 12:20     ` Joel Brobecker
2009-12-20 12:33       ` Alfred M. Szmidt
2009-12-20 14:27       ` Stan Shebs
2009-12-21  7:55         ` Joel Brobecker [this message]

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=20091221075520.GN2788@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=stan@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