Filtering git commits in vim-dev mailing list

[Enan Ajmain]

I think Bram was the only one authoring commits. And he wrote it in
"patch x.y.zzzz: message title" format. Because of this reliable regex,
it was easier to filter out the git-commit emails in vim-dev mailing
list. But now some commits have different formatting. More useful to
be sure (following the conventional commits guideline perhaps?), but
also harder to filter. Any chance any of you have a filtering process?

Currently I'm filtering out emails with "^Commit:" in message body, but
that's unreliable and makes me icky for some reason.

Sounds whiny, maybe even a non-issue, but thought I should ask anyway.

--
Enan

[Christian Brabandt]

On So, 20 Aug 2023, Enan Ajmain wrote:

> I think Bram was the only one authoring commits. And he wrote it in
> "patch x.y.zzzz: message title" format. Because of this reliable regex,
> it was easier to filter out the git-commit emails in vim-dev mailing
> list. But now some commits have different formatting. More useful to
> be sure (following the conventional commits guideline perhaps?), but
> also harder to filter. Any chance any of you have a filtering process?

I started to mirror patches commited to the vim repository directly to
this list, trying to follow Brams practice. However personally I found
it a bit annoying to not send e.g. runtime file patches here, so I
thought it would be beneficial to mirror all patches here.

This is done as part of the repository syncing from git to mercurial and
was a slight simple change.

If this is annoying and nobody uses it anyhow, I can stop it. Or I can
start to use the prefix '^Commit:' in the patch messages.

Best,
Christian
--
"I think it is true for all _ n. I was just playing it safe with _ n >= 3
because I couldn't remember the proof."
-- Baker, Pure Math 351a

[shane.qian]

> If this is annoying and nobody uses it anyhow, I can stop it. Or I can
> start to use the prefix '^Commit:' in the patch messages.

could you also think if possible to reduce the general comments in github to forward to vim_dev mailing list?
since there lots of mails actually dup between this forward and github itself.

// perhaps just Issue/PR-opening and commits-push was worthy to forward to vim_dev?

--
shane.xb.qian

[Enan Ajmain]

On Sun, 20 Aug 2023 11:09:17 +0200
Christian Brabandt <cbl...@256bit.org> wrote:
> [...]

>
> If this is annoying and nobody uses it anyhow, I can stop it. Or I can
> start to use the prefix '^Commit:' in the patch messages.

Assuming by "patch messages," you meant the subject header of patch
emails, then I think a distinguishable pattern (eg, '^Commit:') will be
useful. Not only to filter them automatically with an email client, but
also to search for them in the Google Groups web portal.

TLDR: LGTM.

Thank you for looking into it. And thanks for taking care of Vim.

--
Enan