That was too easy... pmoore@Renegade$ git push Counting objects: 11, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (6/6), 948 bytes, done. Total 6 (delta 3), reused 0 (delta 0) remote: No commit email for refname refs/heads/autodepends remote: No html exported for refname refs/heads/autodepends remote: No archives exported or repo efs-deploy To [email protected]:efs-deploy.git bd97a5f..ce8077f autodepends -> autodepends
Yes, of course I tested a real commit email -- see the list, if you don't trust me :-) Now Steve can stop whining about all the Oops.... On Fri, Jan 13, 2012 at 10:37 AM, Phillip Moore <[email protected]> wrote: > I know a few people are annoyed by the sheer volume of commit emails > we generate, and now that I have taken control of the git hooks, I > think we can trivially fix this. > > The only reason this is happening is because I don't have the ability > to make commits from my current consulting client, so I make all > change on the outside, commit, and then pull them anonymously to build > them internally. While I use topic branches for all of this, the > commit hook sends email for everything pushed to origin, regardless of > the branch. > > I think it makes sense to add a simple wrapper hook that does nothing > is the ref isn't refs/heads/master, This will mean we revert to the > "normal" commit emails, namely only when a completed branch is merged > with master and pushed. You won't have to see all of my "Oops" > commits until the final merge is done. > > I should have this implemented very shortly.... _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
