[RFC] Git mailing list filters
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- git
- Domain
- documentation
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.
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!
- Dominant language
- CSS
- Stars
- 373
- Forks
- 325
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from git/git.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
git/git.github.io#860 · 7 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
git/git.github.io#864 · 5 comments ·
-
Automatically intimate regarding [ANNOUNCE] mails in the current month edition's issue comments? Open
git/git.github.io#863 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
git/git.github.io#862 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
git/git.github.io#830 · 4 comments ·
All issues in git/git.github.io
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
A11y ♿️
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
documentation improve or update documentation priority/low triage
Difficulty 2/5 Half a day Newbie friendliness 86/100
warpdotdev/docs#782 · 1 comment ·