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 20:12:00 -0000	[thread overview]
Message-ID: <20030510201224.GA2881@nevyn.them.org> (raw)
In-Reply-To: <3EBD5ACF.90609@redhat.com>

On Sat, May 10, 2003 at 04:02:23PM -0400, Andrew Cagney wrote:
> >On Sat, May 10, 2003 at 01:50:13PM -0400, Andrew Cagney wrote:
> >
> >>>
> >>>Thank you.  That's all I wanted you to do.  Binutils _already uses
> >>>files generated from frv CGEN input_.  You can go look at it yourself,
> >>>in opcodes/.  So if you're going to contribute a different version of
> >>>the file
> >
> >>
> >>I don't like the implication here.
> >>
> >>If I were to contribute a version of a file that contains code changes 
> >>that impact on other parts of FSF's binutils, I would indicate that up 
> >>front.
> >>
> >>Similarly, if I were to apply a license that in anyway varied from the 
> >>GPL, I'll also indicate that up front.
> >
> >
> >However, since that was obviously the concern - and a reasonable one,
> 
> Which?  The contents, or the license?  No one, other than you, expressed 
> concern over the contents of the file.  Doug even posted a diff.

Sorry then.  I don't remember seeing him do that.

> >since you never phrased your patch in such a way as to say the copies
> >were the same - then it behooves you to say that there are no changes.
> 
> So you think I would engage in unhanded activity such as silently and 
> intentionally modifying a file so that the FSF couldn't rebuild it's 
> sources?  Bizare.

Never mind.  I'll stop trying to be helpful.

> >Your message said nothing about acknowledging the copy of the code
> >already in src.  In fact, I remember you saying it actually came from
> >an internal tree.  The reason for my concern should be obvious.
> 
> I posted that bit of trivia (only moments ago) because it highlights the 
> sillyness of this entire part of the thread.  Should I also mention 
> which internal repository I got the file from (never know, there might 
> be more than one ... :-)?  If you were really so worried about me doing 
> something underhanded, why didn't you yourself take the 30 seconds 
> needed to do a diff (might want to do that anyway, never know .... ;-)?

Damn it, Andrew, I'm not accusing you of anything.  I was originally
concerned that since you deliberately didn't mention that this copy was
the same, that you were taking it from an internal repository which had
some differences from the current code, and maybe you weren't aware
there was already a copy in use.  My point was not that I couldn't do
the diff myself.  In fact, I did.  I wanted you to do it and to post
it, to clear the issue.

> The only important thing here is that this file is [finally] being 
> contributed to the FSF, and that one tiny bit of the mess that Jim 
> Wilson refered to is been resolved.  Beer!!

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-05-10 20:12 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
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 [this message]
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=20030510201224.GA2881@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).