Hi! Thanks for your comments!!
> P.S. You might be interested in using the program git send-email.
> Apparently it makes it really easy to send in a patches series. It's
> actually what GNU Guix contributing guidelines recommends.
My problem is that, in my internal repository, I do many commits for each change (even for each file). The development is progressive.
Then, if I take the commit history to generate my patches, I would generate many spurious patches, making it very difficult to check and apply them.
Even doing a rebase over another branch, the rebase adds the commit history, so I keep the same problem.
And squash commits can be difficult too, because some commits are doing changes in many files.
So, at the moment, I only know dirty tricks to generate the patches.