Actually there is a option on the mailout now to add a diff..
I've not tested it, but I suspect it's not as good and it's never going
to be as flexible as php.net's commit messages.
Anyway, it might be better to sort this out before the mailinglists get
spammed any more..
The rather serious problem with the github mail system for pear is that
it's optional and configurable. pear-cvs is supposed to help all pear
users and developers by giving the a stream of code changes, so they can
see what's going on, pick up on new ideas, fixes to handle changes etc..
Having this as an option for each package on github is just an insane
way to deal with this.
I suggest in the short term, this is done
a) block github from pear-cvs, and see if we can disable all the
packages from mailing in bulk.
b) Move the packages to git.php.net (and turn github into a dumb mirror)
c) use php.net's commit mailer to distribute emails
d) set up github as a dumb mirror (read only) of most packages
if developer want to 'prefer' github over git.php.net
a) recommend they add a postcommit hook to github
b) postcommit just triggers a url on git.php.net to pull the repo
changes, and hence fires of the standard mail.
Thoughts...
Regards
Alan
On Sunday, April 15, 2012 03:05 PM, Christian Weiske wrote:
> Hello Alan,
>
>
>> Commit messages without diff's are about as useless as messages
>> saying "You have a message click here to read it"
> I've written github about this issue once and got the reply that I
> should fix it myself and send them a pull request :/
>
--
PEAR Development Mailing List (
http://pear.php.net/)
To unsubscribe, visit:
http://www.php.net/unsub.php
