public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Alan Modra <amodra@bigpond.net.au>, binutils@sources.redhat.com
Subject: Re: [rfa] FRV input files
Date: Sat, 10 May 2003 14:42:00 -0000	[thread overview]
Message-ID: <20030510144231.GA8030@nevyn.them.org> (raw)
In-Reply-To: <3EBC4046.70003@redhat.com>

On Fri, May 09, 2003 at 07:56:54PM -0400, Andrew Cagney wrote:
> >Andrew, can we do this differently?
> >
> >Something that has been mentioned several times, but I'm not sure is
> >clear to you, is that these files already exist in src/cgen/cpu/.
> 
> >Those copies are _not_ exactly the same as the ones you're adding.
> >In order to make sense of this patch, could you move them to their new
> >home separately from changing the license or whatever other changes are
> >incorporated in the patch below?
> 
> From the FSF's point of view, this is brand new code and, as such 
> should, from day one be given the correct (C) and correct license.  To 
> do otherwize would be confusing.
> 
> Think of this as part of a brand new port that you've never seen before. 
> Even though the contributor might have a separate repository containing 
> a very long history of changes, all that is irrelevant to the FSF.  From 
> the FSF's point of view, the file is ``born'' the day someone 
> contributes it.

Now that's ridiculous.

Please at least post a diff from the version already _in the repository
you are asking permission to commit this patch to_.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-05-10 14:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03  0:50 Andrew Cagney
2003-05-03  1:07 ` Doug Evans
2003-05-03  1:10   ` Doug Evans
2003-05-03 18:29   ` Andrew Cagney
2003-05-03 20:37     ` Doug Evans
2003-05-03 22:06       ` Andrew Cagney
2003-05-03 23:21         ` Doug Evans
2003-05-04 11:27         ` Frank Ch. Eigler
2003-05-04 15:13           ` Andrew Cagney
2003-05-05 13:36             ` Frank Ch. Eigler
2003-05-06 21:42               ` Andrew Cagney
2003-05-07 16:20                 ` Doug Evans
2003-05-07 18:34                   ` Andrew Cagney
2003-05-07 19:19                     ` Doug Evans
2003-05-07 19:46                       ` Andrew Cagney
2003-05-07 19:56                       ` Andrew Cagney
2003-05-09 16:24                       ` Andrew Cagney
2003-05-04 14:27 ` Andrew Cagney
2003-05-04 15:37   ` Andrew Cagney
2003-05-09 15:10 ` Andrew Cagney
2003-05-09 16:21   ` Daniel Jacobowitz
2003-05-09 23:56     ` Andrew Cagney
2003-05-10 14:42       ` Daniel Jacobowitz [this message]
2003-05-10 16:04         ` Andrew Cagney
2003-05-10 16:08           ` Daniel Jacobowitz
2003-05-10 17:50             ` Andrew Cagney
2003-05-10 18:09               ` Daniel Jacobowitz
2003-05-10 20:02                 ` Andrew Cagney
2003-05-10 20:12                   ` Daniel Jacobowitz
2003-05-11  3:18           ` Daniel Berlin
2003-05-10 12:49   ` Alan Modra
2003-05-10 15:30     ` Andrew Cagney
2003-05-12 10:55   ` Nick Clifton
2003-06-03 15:42 ` 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=20030510144231.GA8030@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).