From: Sitaram Chamarty Date: Mon, 16 Feb 2009 01:27:51 GMT Subject: Re: [RFC - draft] List of proposed future changes that are backward incompatible Message-ID: In-Reply-To: On 2009-02-15, david@lang.hm wrote: > On Sun, 15 Feb 2009, Junio C Hamano wrote: >> * git-push to update the checked out branch will be refused by default >> >> Make "git push" into a repository to update the branch that is checked >> out fail by default. >> >> http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 > > If I understand this one, it will cause grief for quite a few people. > > I have a public repository that I push to and then have a trigger that > checks out the current version, compiles it, publishes the compiled > version, sends an announcement, etc > > if I am understanding the purpose of this change, you would prohibit the > update from taking place. I didn't read the *entire* thread but I do believe prohibit is too strong. It's only the default behaviour that is being changed -- in your situation you'd just set receive.denyCurrentBranch to either 'warn' (the current default) or 'ignore'.