Skip to content

email-template: Add also patch subject #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pevik wants to merge 1 commit into
base: master
Choose a base branch
from
Open

email-template: Add also patch subject #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions rules/email-template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,22 +105,30 @@ LTP AI Reviewer
### Issues found (multi-patch series)

If there are issues in one of the patches, reply once, to the first patch.
Use `--- [PATCH N/M] ---` markers between per-patch comments. ONLY include
patches that have findings.
Separate per-patch comments with a marker holding the full subject line of
that patch, copied verbatim from its `Subject:` header:

```
--- [PATCH v2 15/33] keyctl23: Test KEYCTL_RESTRICT_KEYRING builtin_trusted
```

Keep the marker on a single line even if it exceeds 78 characters, and
NEVER shorten it to just `[PATCH N/M]`. ONLY include patches that have
findings.

```
Hi <firstname>,

On <date>, <author> wrote:
> <cover letter or first patch subject line>

--- [PATCH 1/M] ---
--- <patch 1 subject line>

> [relevant diff hunk or code line]

<comment>

--- [PATCH 3/M] ---
--- <patch 3 subject line>

> [relevant diff hunk or code line]

Expand Down