Relicensing

Relicensing

[Richard Stallman]

Thanks very very much for relicensing Emacs 22.

Would someone else please relicense the trunk
and unicode-2?

Re: Relicensing

[Dan Nicolaescu]

Richard Stallman <rms@gnu.org> writes:

  > Thanks very very much for relicensing Emacs 22.
  > 
  > Would someone else please relicense the trunk
  > and unicode-2?

How about multi-tty?

Re: Relicensing

[Stefan Monnier]

>> Thanks very very much for relicensing Emacs 22.
>> 
>> Would someone else please relicense the trunk
>> and unicode-2?

> How about multi-tty?

This should all be taken care of the "automatic" merging from the 22 branch
to the trunk, to the multi-tty and unicode branches.  After all the merging
is done, we will want to go through the result to fix the things that were
missed (e.g. new files etc...).


        Stefan

Re: Relicensing

[Richard Stallman]

    This should all be taken care of the "automatic" merging from the 22 branch
    to the trunk, to the multi-tty and unicode branches.

I didn't realize this would be easy.  Miles, thank you for
doing it.]

Re: Relicensing

[Richard Stallman]

    How about multi-tty?

The thing to do with multi-tty now is merge it into the trunk.
Karoly says he can't do it.  Who would like to do it?

Re: Relicensing

[Glenn Morris]

Richard Stallman wrote:

> Would someone else please relicense the trunk and unicode-2?

I don't mind doing the trunk as well (if it's easier for me to do this
than for Miles to merge the changes via arch), but I draw the line at
doing unicode-2 in addition. Surely it can wait until after unicode-2
is merged to the trunk? Alternatively, another good reason to merge
unicode-2 now! :)

(with-flogging-a-dead-horse
  I really think the work involved in continuing to sync trunk and
  unicode-2 is greater than that that would be involved in porting
  changes from a merged unicode-trunk to the release branch.)