Re: [git] web/master.git branch master updated. 8181453
| From: | Christopher Jones | Date: | Tue, 24 Jan 2012 20:28:38 +0000 |
| Subject: | Re: [git] web/master.git branch master updated. 8181453 | ||
| References: | 1 2 3 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-12920@lists.php.net to get a copy of this message | ||
On 01/24/2012 11:33 AM, David Soria Parra wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/24/2012 10:21 AM, Derick Rethans wrote:Do option 3 to the one mail list. Use a subject prefix so we can filter push from commit mails. And/or do option 4. Chris -- Email: christopher.jones@oracle.com Tel: +1 650 506 8630 Blog: http://blogs.oracle.com/opal/Hi, could something be done about the commit spam subjects? It was mightly useful to have the paths and the commit messages in there.The problem here is that you can push multiple changesets at once and the header will get very long. Max subject length are arbitrary. I understand that it's useful, so you suggested having a mail for each commit instead of each push. I prefer mails per push as they are the only documentation of who pushed what. In case someone pulls from a person that doesn't have karma and pushes it, I want to ask that person why and what. So the pushmails is useful for me and gives me a good overview over the overall change. So the option is to (1) have commit mails or push mails only. (2) both (3) send one type of mail to a separate mailinglist (4) change the pushmail format to something useful.