On Tuesday 2009 January 13 16:18:52 R. Tyler Ballance wrote: >On Tue, 2009-01-13 at 16:06 -0600, Boyd Stephen Smith Jr. wrote: >> 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. > >Looks good, thanks; sorry I missed it, didn't even think to look at the >git-config(1) page for such an option. I didn't really know about it until earlier this week. I was expecting to be able to do a non-ff push to one of my repositories and it didn't work because this was set "behind my back". (I'm not sure when it got added, but I don't think the shared repositories I set up with git 1.4.4.4 had it, so I wasn't expecting it.) >I'm assuming this will actually cover the rebase -i case as well? I don't know exactly what you mean. It prevents fast-forwards, so once a commit is "visible" on one of your central branches, it won't ever go away. (You can, of course, use git revert to undo it's changes.) As others mentioned, now would be a good time to look at receive.denyDeletes and/or a custom hook as well. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.
