On Tue, 2009-01-13 at 16:06 -0600, Boyd Stephen Smith Jr. wrote: > 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.
Attachment:
signature.asc
Description: This is a digitally signed message part
