Matthias Paulmier <matthias.paulm...@etu.u-bordeaux.fr> writes: > I sure can, I was feeling like it was a bit long but for some reason > thought it was better that way.
No problem, the appropriate granularity for patches is a subjective matter. However in practice software projects tend to agree that new features, bug fixes, and file renaming/moving should be done in separated commit/patches. > Can I send multiple patches at once (in one email as attachements), or > should I send them each on their own? Both are possible, and convenient for me. To be more precise, if you do it by hand with attachments, it will be simpler to include all those attachments in one email. Alternatively If you use ‘git send-email’, by default it sends the patches in response to the first patch or the “cover letter” if you made one. In your case you it is important to add the ‘--in-reply-to="<878t4fhddt....@mpaulmier.home>"’ option to ensure that your first patch is sent in response to the current thread. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
