git / git/git.github.io

[RFC] Git mailing list filters

未關閉
#818 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
CSS
星號
373
分支
325
平均合併
4 天 18 小時
30 天內合併 PR
1

描述

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!

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

檢視 git.github.io 的文件結構,尤其是可能存在的 Hacking Git 頁面,並將提議的 Gmail 篩選器與網站現有內容進行比較。完成的標準是選擇適當的位置,並清楚記錄有用的郵件清單篩選器,同時註明如果 Gmail 語法無法支援 release 篩選,則不涵蓋該功能。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
git
領域
documentation
Issue 類型
文件
難度
3/5
預估耗時
1-2 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。