public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: #!/usr/bin/env tclsh
Date: Thu, 08 Jan 2009 18:21:00 -0000	[thread overview]
Message-ID: <49664410.8090704@eCosCentric.com> (raw)
In-Reply-To: <49663D09.6070902@dallaway.org.uk>

John Dallaway wrote:
> [ moving to ecos-maintainers list ]
> 
> Hi Jifl
> 
> Jonathan Larmour wrote:
> 
>> John Dallaway wrote:
>>
>>> This patch simplifies the #! magic used to invoke Tcl scripts by using
>>> "/usr/bin/env tclsh" to find the tclsh executable. Very old Cygwin
>>> installations providing only tclsh83.exe or cygtclsh80.exe are no-longer
>>> supported. Checked-in.
>> Can you please refrain from further non-trivial changes until you have a
>> copyright assignment.
> 
> I do not consider these changes to be copyrightable. Simplification of
> the #! magic for Tcl scripts is more trivial in nature than the
> documentation references I added late last year which we agreed were not
> copyrightable.

Actually you stated that, I did not. I said "probably" and said it was very
much thin ice. I was not happy about it. And I asked you to include those
on the assignment request regardless. This is why I did not ask you to
revert the patch - with a random net contributor I would have.

> What aspect of these changes do you consider to be copyrightable?

It's sailing close to the wind. IANAL and I don't want to need to talk to
one, so under the principle of keeping it simple I have a preference for
19k patches not going in without assignment, for the sake of waiting a very
short time. That's why I was asking for no more, rather than asking you to
revert it.

Thinking about it, resubmitting the assignment request form is probably
OTT. The FSF does not include this information on the assignment itself
IIRC: but they do keep records of the information for legal reasons. So
maybe it is adequate to simply inform assign (AT) fsf.org of the extra
files. If you can do that, I'd be happy. But still hold back on anything
non-trivial in the (unlikely) event they aren't happy.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

  reply	other threads:[~2009-01-08 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <496635B7.8060808@dallaway.org.uk>
     [not found] ` <49663810.3010202@eCosCentric.com>
2009-01-08 17:51   ` John Dallaway
2009-01-08 18:21     ` Jonathan Larmour [this message]
2009-02-06 12:24 ` Bart Veer
2009-02-06 12:38   ` Gary Thomas
2009-02-06 12:53     ` Bart Veer
2009-02-06 13:49   ` John Dallaway
2009-02-06 14:03     ` Gary Thomas

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=49664410.8090704@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=john@dallaway.org.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).