Kevin Fenzi wrote: > On Tue, Oct 29, 2019 at 02:19:00PM -0400, Stephen John > Smoogen wrote: >> I didn't see anything patched on there so I am not sure >> what to review. > > git-send-email always for some reason sends the actual > patch as a followup. So, look for the first followup to > the orig message in the thread... Hmm, that's not behavior I've ever seen from git send-email. Is the git format-patch --thread option or format.thread config variable set along with the --thread option to git send-email? The defaults generally work. Now, if we're talking about the ancient 1.x versions in RHEL, maybe the defaults were different. Though even then, I don't recall having this issue. The one change I can recall that's in the vicinity was from deep nested threads (where each patch was a reply to the previous one) to shallow threads (where each patch in a series is a reply to the cover-letter). That shouldn't come into play at all with a single patch. Is there a doc covering the process which I could follow and try to reproduce (and hopefully help to avoid this)? -- Todd
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
