On 14/09/2012 03:28, Marvin Humphrey wrote:
On Wed, Sep 12, 2012 at 2:24 PM, Nick Wellnhofer <[email protected]> wrote:
I wonder a bit about the next sentence on that page:
"A common configuration is to prevent non-fast-forward updates on any ref
that matches the following patterns:"
Preventing non-fast-forward updates is what you describe below. But you can
also have merges aren't fast-forward, but don't rewrite history. It probably
only means that enforcing fast-forward updates is one way to make sure that
you never rewrite history.
Yes, I'm all but certain that the intent is to avoid rewriting history[1].
I was wrong anyway. I didn't realize that a proper merge actually is a
fast-forward update.
Rewriting history can be useful if some really stupid mistake happens
where it's better to completely undo the changes. Otherwise, you'd have
to revert the changes with another commit. But that's not a big deal either.
Nick
