The create-patch-request script creates patches as replies to a cover letter, in the form of an email thread. If further revisions are sent to the mailing list without referencing to the first revision, these new revisions are not identified at the mailing list as part of the original thread, but as a new thread instead.

This behavior may not be seen as an issue at the mailing list, but at the OE-Patchwork tool, where any patch or series identified as part of a thread is added to the existing series in the form of a new revision, missing references may cause to have broken threads, thus producing individual series for revisions of the same series (this is specially true if the new revision differs in patch quantity or title from the original).

The proposed solution is to add the "[-t in_reply_to]" option to the create-pull-request script (where "in_reply_to" is the original cover letter's Message-Id), to ensure that the reference to the original thread is added to the new patch/series so it can be identified as part of it. With this option, the cover letter for any new revision is created as reply to the original cover letter, thus ensuring that OE-Patchwork will recognize the new series as a revision of an existing one.

The "-t" option would not be required, so the current script functionality would remain the same if "-t" is missing.