Mohsin Kaleem <mohkale@kisara.moe> writes:

>
> I'm not sure what you mean by the first two patches occur twice, could
> you clarify so I can fix the issue? I've dropped the reverted patch and
> rebased on top of master so you shouldn't have any issues applying the
> patch series now.
>

For reference, just look at the first and third attachements to your
message. These (somehow) describe the same commit / patch. In any case
it is fixed in the next iteration using git send-email.

>> If possible, please use git send-email to send one-patch-per-message, it
>> makes reviewing in notmuch-emacs much easier for me.
>
> I just used git send-email to send the patch series (I assume it'll be
> sent separately). I'd like to ask:
> + How do you manage git and email workflows like this for reference?
> I haven't found any documentation about it when searching.

Some general advice is at https://git-send-email.io/

> + Is there a way to do this with notmuch involved (ideally through emacs
> and Magit)?

I use git send-email from the command line to send patch series. To
review them, I read the resulting threads and reply to individual
patches / commits / messages.

To apply patch series, you may want to try mailscripts [1]. The
description makes it sound debian-centric, but I guess the elisp
functions like notmuch-extract-thread-patches are portable.

Finally I have some git aliases to apply individual patches:

[alias]
	nmam = "!f() { notmuch extract-patch $1 | git am -; }; f"

[alias]
	nmam8 = "!f() { notmuch extract-patch $1 | email-to-8bit |  git am -; }; f"

[alias]
	nmam3 = "!f() { notmuch extract-patch $1 | git am -3 -; }; f"


These versions rely on notmuch-extract-patch, from mailscripts [1], but
if you don't have that "notmuch show --format=raw" works almost as well.

[1]: https://github.com/spwhitton/mailscripts
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org