On Wed, Sep 12, 2012 at 2:24 PM, Nick Wellnhofer <[email protected]> wrote:
> Although I don't have any Python experience, I can offer to create the INFRA
> issue and act as point person.
+1
> But we should probably call a vote on this procedural issue first.
+1
> 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].
Marvin Humphrey
[1] Background:
http://git-scm.com/book/en/Customizing-Git-Git-Configuration#Server-Configuration
