Re: Contributing other person's work

[Stefan Monnier <monnier@iro.umontreal.ca>]

> How does the workflow work exactly?̊̈
> If I send the patch by email, does one of the core contributors apply the
> patch onto the current HEAD of remote?

Yes, that's one way.  Another is to point to a Git branch.
I'm not sure whether we want the faithful commit history in this case:
I usually like it, but if there's been too many "merge from master"
that end up drowning the real commits, it might be worth the trouble of
reworking the history a bit (e.g. going back to the last real commit
merge that into master).  Also, the commit messages may require
improvements, which would again require rewriting the history.

>> He has: it's on file and everything.
> As I haven’t signed before, can I ask how to sign the copyright assignment?

Sure: fill the form below and email it as instructed to the FSF so they
can send you the relevant paperwork to sign,


        Stefan


Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]
Emacs

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]