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. Thanks anyway El mar., 11 ago. 2020 a las 8:27, Joshua Branson (<jbra...@dismail.de>) escribió: > > Almudena! Nice work on this! and Holy cow! Your English is getting > fantastic! It inspires me, when I see how much you're learning on this > SMP project. Keep up the good work! > > 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. > > https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html > > P.P.S. I feel slightly silly giving tips, when everyone else on this > email list is several orders of magnitude a better developer than I am. > In fact, I probably only understood 50% of what this email chain was > about. I hope this off topic email is not offensive or annoying to > anyone. I just wanted an excuse to encourage and praise Almudena > publicly! > > -- > Joshua Branson > Sent from Emacs and Gnus > >
