Re: [patch #6758] Add support for Atari FreeMiNT OS

[Jim Meyering]

Alan Hourihane wrote:
> Hi Jim,
>
> On Sat, 2009-02-28 at 17:29 +0100, Jim Meyering wrote:
>> Alan Hourihane wrote:
>> >   <http://savannah.gnu.org/patch/?6758>
>> >                  Summary: Add support for Atari FreeMiNT OS
>> >                  Project: GNU Core Utilities
>>
>> Thanks for the work.  I've included that patch below for convenience.
>> Most of it applies to gnulib, so I've Cc'd its list.
>> This is large enough that you'll have to fill out
>> copyright papers before we can use the changes.
>> For details and other relevant guidelines (most apply
>> to gnulib, too), see
>>
>>   http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING
>>
>> in particular, I see that indentation/brace style in mountlist.c
>> does not conform, and there are some trailing blanks.
>
> Now that the gnulib portions are addressed, what's left to do for these
> files...
>
>>  lib/mountlist.c    |   80 
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  src/df.c           |    5 +++
>>  src/uptime.c       |    7 ++++
>>  11 files changed, 123 insertions(+), 1 deletion(-)
>
> The above are copyright Frank Naumann <fnaumann-at-freemint.de> and
> Frank is said it's o.k. to push these upstream.

The changes to mountlist.c (which is in gnulib, by the way)
are large enough that Frank has to follow the process
described in coreutils contribution guidelines:

  http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING

    Copyright assignment
    ====================
    If your change is significant (i.e., if it adds more than ~10 lines),
    then you'll have to have a copyright assignment on file with the FSF.
    Since that involves first an email exchange between you and the FSF,
    and then the exchange (FSF to you, then back) of an actual sheet of paper
    with your signature on it, and finally, some administrative processing
    in Boston, the process can take a few weeks.

    The forms to choose from are in gnulib's doc/Copyright/ directory.
    If you want to assign a single change, you should use the file,
    doc/Copyright/request-assign.changes:

        
http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=blob;f=doc/Copyright/request-as
    sign.changes;hb=HEAD

    If you would like to assign past and future contributions to a project,
    you'd use doc/Copyright/request-assign.future:

        
http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=blob;f=doc/Copyright/request-as
    sign.future;hb=HEAD

    You may make assignments for up to four projects at a time.

    In case you're wondering why we bother with all of this, read this:

        http://www.gnu.org/licenses/why-assign.html

Once that's done, and you get email'd confirmation from the FSF
that they've received the signed forms, please ping the list.