To me, it's more along the lines of "let git help me not make the
mistake of hacking on a six-week old codebase when I've explicitly asked
it to merge these and those remote tracking branches into these and
those local branches". Not updating those branches when there *are*
changes on them is something users can understand and will probably also
appreciate, but the reason for not allowing even fast-forwards escape me.
Well, I knew that much from the start so I didn't ask you to, and since
you seem to fail to grasp what I had in mind, I'm sure you'd botch the
implementation anyway. Thanks for not quite offering though ;-)
I'm sure you'll review the patch though, and I'm equally sure I will
appreciate your technical comments rather a lot more than this current
bickering about a feature it seems I can't express clearly enough in words.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html