From: Jan Hubicka <jh@suse.cz>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Jan Hubicka <jh@suse.cz>, Neil Booth <neil@daikokuya.co.uk>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: GCC 3.3 for OS/2
Date: Sat, 08 Feb 2003 19:31:00 -0000 [thread overview]
Message-ID: <20030208193123.GC28986@kam.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0302081922520.29180-100000@artax.karlin.mff.cuni.cz>
> > > Mikulas Patocka wrote:-
> > >
> > > > No. BTW - I ripped some parts of my port from EMX GCC 2.7.2.1 (it is also
> > > > GPLed) -- does it mean that Eberhard Mattes needs copyright assignment
> > > > too?
> > >
> > > I have no idea as I know nothing about that compiler.
> > In any case, when some code has been cut&pasted from someones else work,
> > he needs assignment as well. But I believe Mattes has it already as he
> > is working on EMX for some time already.
>
> He never pushed his changes into main gcc distribution. I'll ask him, if
> he is going to sign it. If he won't sign it, I could go through the patch
> and attempt to rewrite parts from EMX, however I don't really know, how to
> rewrite a lot of one-line changes. Do small few-line changes matter?
There is exception for very small patches, but I am not sure whether
collection of many very small patches still has such exception.
Honza
>
> Mikulas
next prev parent reply other threads:[~2003-02-08 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 15:01 Mikulas Patocka
2003-02-06 22:53 ` Neil Booth
2003-02-07 9:03 ` Mikulas Patocka
2003-02-07 21:51 ` Neil Booth
2003-02-07 22:26 ` Jan Hubicka
2003-02-08 18:29 ` Mikulas Patocka
2003-02-08 19:31 ` Jan Hubicka [this message]
2003-02-07 22:27 ` Joe Buck
2003-02-07 22:41 ` Gerald Pfeifer
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=20030208193123.GC28986@kam.mff.cuni.cz \
--to=jh@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=neil@daikokuya.co.uk \
/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).