On Wed, Jul 3, 2013 at 12:06 PM, Jonathan del Strother
> I'm struggling to think of instances where I wouldn't want this
> CAS-like behaviour. Wouldn't it be better to make it the default when
> pushing, and allowing the current behaviour with "git push
> --blind-force" or something?
I believe I agree with you. I guess the reason this hasn't come up
before is that by far most of the pushes we do are either
fast-forwarding, or pushing into a non-shared repo (e.g. my own public
repo), and this safety only really applies when we're forcing a
non-fast-forward push into a shared repo...
Johan Herland, <jo...@herland.net>
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html