On Thu, Dec 13, 2012 at 2:43 PM, Chip Childers <[email protected]> wrote: > On Thu, Dec 6, 2012 at 1:09 PM, Rohit Yadav <[email protected]> wrote: >> >> On 06-Dec-2012, at 9:17 AM, Joe Brockmeier <[email protected]> wrote: >> >>> On Thu, Dec 6, 2012, at 11:14 AM, Rohit Yadav wrote: >>>> For writing commit messages, I think branch name may not be useful but >>>> what your commit is doing is more important maybe? >>> >>> As I understand it, this is a proposal for the subject line of the >>> emails - not how the commit messages are written. >> >> Okay, is it for the git hook to send emails with branch names in the message >> lines? Yes, that would be great! >> Oops, got confused. >> >> Regards. >> > > Just so everyone knows, I'm watching a thread over on the > infrastructure list where it's being made very clear that custom hooks > are simply not going to be supported. Not sure the implications to > this proposal, but I think that we need to be aware that this seems to > be a standard infra team position that's well established.
Yes, I've tried to say this previously. Per-project commit hooks are simply not welcome; they are a maintenance nightmare. ASF-wide commit hooks might be acceptable depending on functionality and impact to performance. --David
