| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com> |
| Cc: | Erikjan Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commit message / hash in commitfest page. |
| Date: | 2019-04-13 20:48:49 |
| Message-ID: | 5CB24B31.9010700@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/13/19 15:56, Tomas Vondra wrote:
> I think it might be useful to actually have that directly in the CF app,
> not just in the thread. There would need to a way to enter multiple
> hashes, because patches often have multiple pieces.
The CF app already recognizes (some) attachments in the email thread
and makes them directly clickable from the CF entry page. Could it do
that with commit hashes, if found in the body of an email thread?
Gitweb does that pretty successfully with commits mentioned in
commit messages, and github does it automagically for text in issues
and so on.
Maybe it could even recognize phrases like "commit 01deadbeef closes
cf entry" and change the cf entry state, though that'd be gravy.
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2019-04-13 21:15:26 | Re: Commit message / hash in commitfest page. |
| Previous Message | Tomas Vondra | 2019-04-13 20:42:52 | Re: Should the docs have a warning about pg_stat_reset()? |