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.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/