David Bremner <da...@tethera.net> writes: Hi, thanks for all the advice :-). I'm still quite unfamiliar with mailing-list based workflows so I keep developing like I'm on GitHub.
> I think the patch series needs a bit of cleanup still. The first two > patches occur twice and then a later patch is reverted (so presumably > those two can be dropped as well). > > You may also want to rebase against master before resending, since I > have just a applied some changes to the emacs UI code that might collide > with yours. 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. > 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. + Is there a way to do this with notmuch involved (ideally through emacs and Magit)? -- Mohsin Kaleem _______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
