git / git/git.github.io

[RFC] Git mailing list filters

Open
#818 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
373
Forks
325
Avg merge
4d 18h
Merged PRs (30d)
1

Description

Hello!

I was discussing with @chriscool about adding instructions to git.github.io about filtering messages from the Git mailing lists. I don't know exactly which would be the best page to place them (perhaps Hacking Git? or a new page dedicated to dealing with communication?).

This work for me (please note that I use GMail and I'm following its searching syntax):

Type Folder Mark as read Search string
Messages including me Inbox No (default behavior)
Patch Git/Patches Yes from:(-<my address>) subject:PATCH (list:git@vger.kernel.org AND -to:<my address>)
What's cooking Git/What's cooking No from:(-<my address>) subject:(What's cooking in git.git) (list:git@vger.kernel.org AND to:-<my address>)
Rev News Git/Rev News No from:(-<my address>) subject:("[ANNOUNCE] Git Rev News") (list:git@vger.kernel.org AND to:-<my address>)
Other Git/Discussion No from:(-<my address>) subject:(-PATCH -"What's cooking" -"[ANNOUNCE] Git Rev News") (list:git@vger.kernel.org AND to:-<my address>)

I would like to hear you if you have any comments on these filters. I want do to something for filtering Git releases but GMail's syntax isn't powerful enough to do that (unless if I do some tricks checking the messages bodies, which is a fragile assumption).

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the git.github.io documentation structure, especially the possible Hacking Git page, and compare the proposed Gmail filters with the existing site content. Done means choosing an appropriate location and documenting the useful mailing-list filters clearly, while noting that release filtering is not covered if Gmail's syntax cannot support it.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.