Re: Removing options from build

From: R. Tyler Ballance <tyler@slide.com>
Date: Jan 13, 2009, 22:18 UTC
Message-ID: <1231885132.14181.38.camel@starfruit>
In-Reply-To: <200901131606.04634.bss@iguanasuicide.net>

On Tue, 2009-01-13 at 16:06 -0600, Boyd Stephen Smith Jr. wrote:

Show 15 quoted lines

> On Tuesday 2009 January 13 15:43:22 R. Tyler Ballance wrote:
> >One of our developers "discovered" the --force option on `git push` and
> >used it without taking the appropriate care and hosed one of the project
> >branches we have running around in our central repository.
> 
> Reflogs should let you recover from this.
> 
> >Besides a vigorous flogging, we're looking at other ways to prevent this
> >sort of thing from happening again;
> 
> receive.denyNonFastForwards
>         If set to true, git-receive-pack will deny a ref update which
>         is not a fast forward. Use this to prevent such an update via a
>         push, even if that push is forced. This configuration variable
>         is set when initializing a shared repository.

Looks good, thanks; sorry I missed it, didn't even think to look at the git-config(1) page for such an option.

I'm assuming this will actually cover the rebase -i case as well?

Cheers

-- 
-R. Tyler Ballance
Slide, Inc.