Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: <binutils@sources.redhat.com>,  <gdb@sources.redhat.com>
Subject: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?
Date: Sat, 14 Sep 2002 02:42:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.30.0209140532250.96617-100000@dair.pair.com> (raw)
In-Reply-To: <3D815E4F.6090407@ges.redhat.com>

On Thu, 12 Sep 2002, Andrew Cagney wrote:
> > On Thu, 12 Sep 2002, Andrew Cagney wrote:
> >
> >> I'd like to propose a new directory:
> >>
> >> 	src/include/cpu/
> >>
> >> The directory would contain the CGEN .cpu and .opc input files used to
> >> generate CGEN based binutils disassemblers, assemblers and (?)
> >> relocations.  GDB could also use these files when generating CGEN based
> >> simulators.
> >>
> >> The directory would be part of the FSF's BINUTILS package and, hence,
> >> would be covered by the BINUTILS copyright assignment.
>
> > Being part of binutils requires copyright for all parts to
> > belong to the FSF.
>
> ``The [new, initially empty] directory would be part of the FSF's
> BINUTILS package and, hence, would be covered by the BINUTILS copyright
> assignment.''

Thanks for the clarification.  I didn't see the "initially
empty" part at all implied by "new".  Frankly I think it's the
wrong solution to any copyright problem to introduce *another*
directory for these files.  Also, it seems odd to put it solely
under the binutils domain.  What about CGEN ports only intended
for simulators?

brgds, H-P


  reply	other threads:[~2002-09-14  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 18:10 Andrew Cagney
2002-09-12 18:43 ` DJ Delorie
2002-09-12 19:26   ` Doug Evans
2002-09-12 19:15 ` Hans-Peter Nilsson
2002-09-12 20:41   ` Andrew Cagney
2002-09-14  2:42     ` Hans-Peter Nilsson [this message]
2002-09-14  8:02       ` Doug Evans
2002-09-12 19:50 ` Ben Elliston
2002-09-12 20:16   ` Doug Evans
2002-09-12 21:19     ` DJ Delorie
2002-09-12 21:37       ` Doug Evans
2002-09-13  8:34     ` Frank Ch. Eigler
2002-09-26 17:04 ` Andrew Cagney

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=Pine.BSF.4.30.0209140532250.96617-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=ac131313@ges.redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.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