> Uwe Brauer <oub@mat.ucm.es> writes:

> I am afraid I don't understand what you are trying to say here.  It is
> true that you should check if new contributors have signed the FSF CA,
> but how does that related to Git branches?

Sorry for not having explained this better. Once we have moved to github
(which I hoped to have done already), there are two scenarios

    1. We proceed as before, that is around 4 authors, all of them
       having signed the FSF paper, continue to contribute.

    2. Out of sudden, because it is github and a people love pull
       requests, a lot of contributions pop up, maybe from people
       working for matlab, or for any other reasons. These contributions
       might introduce new sexy features or bug fixes or both, but the
       authors are somehow lazy to sign the FSF papers (it was quite a
       bit of ordeal to have all contributors signed). In that scenario,
       it might be a good idea to have 2 branches,

       1. one for commits with authos having signed the FSF papers

       2. One for commits with new contributions but with non-FSF
          authors.
          

From experience it is best to be prepared. I know git is flexible: I can
create, rename and delete branches, but because git is so flexible the
process is not failsafe, name-rev does not always assign to a commit the
correct branch, which makes me nervous (being a mercurial user).


> Disregard this, I seem to have attached the wrong diff.

Ok. 

> OK, just ping me when you think the cleanup process is done, and I can
> tell you if anything remains to be done before adding the package.

Hopefully soon.


-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine.