I know a number of developers of guix here are also Magit fans. When you have a patchset, how do you usually send it... and in the reverse direction, how do you usually go about applying a patchset? I'm going to admit awkwardly that what I've done historically is generate patches one by one and manually start a thread but it's obviously suboptimal. (I also use mu4e.) Not urgent, just wondering! There has to be a better way than what I've done. ;)
Hi Christopher, I usually use the log in Magit, highlight the commits I want and then use W c c to create a patch set. I submit them as attachments on one email usually (I use dired and gnus for that). I know threading (one patch per email) works better with tools like patchwork but I don’t want to drop to git send-mail. One caveat is that I’m not sure how well my patch sets are received. I will accept any criticism there. Curious to know how others work, John
[-- Attachment #1: Type: text/plain, Size: 321 bytes --] For me, "git send-email" unpredictably drops some patches without notice. I don't know if it's a bug with our package or with upstream. About Magit, I'd also recommend to "insert base commit" when creating the patchset. Something like "W c C-m b ... c". Cheers! -- Pierre Neidhardt https://ambrevar.xyz/ [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 487 bytes --]
Thank you to both of you! I will give these approaches a try.
Pierre Neidhardt writes:
> For me, "git send-email" unpredictably drops some patches without
> notice. I don't know if it's a bug with our package or with upstream.
>
> About Magit, I'd also recommend to "insert base commit" when creating
> the patchset. Something like "W c C-m b ... c".
>
> Cheers!