Mitch Capper wrote: > *Excess Commits / proper gnu submission* > As I have been at this for awhile while the branches are often rebased on > top of master they have far more commits than required. If these things > are for inclusion into the main repo certainly I can reduce it down to > single feature commits and patches per the docs. I do have contributor > agreements already in place with GNU.
It's good that you have already dealt with the copyright papers exchange with the FSF in 2023. This way, you can start the upstreaming of your patches right away, without delay. Please present patches one-by-one and with explanations. We cannot deal with 10 patches in a single day; need to pipeline them. Please present patches at attachments, not inline in the mail body (because some mailers, especially gmail, don't support this well). Please don't put explanations into the commit message. Rather, put a reasonable amount of explanations into comments, and the rest into the mail. Each commit should be an indivisible change to a module or set of modules. If you have several commits to which the same explanation applies, you can send them all within a single mail. I don't intend to look at the past history in your git repo, but instead I will rely on your explanations. Bruno
