On Mon, Aug 26, 2013 at 4:16 AM, Matthieu Moy
> Matthieu Moy <matthieu....@grenoble-inp.fr> writes:
>> Junio C Hamano <gits...@pobox.com> writes:
>>> Matthieu Moy <matthieu....@grenoble-inp.fr> writes:
>>>> How would I do that? The update to the remote namespace is done by Git,
>>>> not by the remote-helper.
>>>> OK, I'm now convinced that my solution is the right one. The
>>>> alternatives are far more complex and I still fail to see the benefits.
>>> Sounds like a plan, even though it smells like the "update is done
>>> by Git" that does not have any way to opt-out may be the real design
>>> mistake and your "solution" is a work-around to that.
>>> Would it be a possibility to make it tunable, perhaps by introducing
>>> a capability on the remote-interface side that allows you to tell it
>>> not to mess with the remote namespace?
>> Ideally, it would be possible to ask for a non-update without a fatal
>> error on old Git versions, but this is not possible (hence, my fix is
>> the "portable" one, that works on Git 1.8.4).
>> But that's probably the best we can do now.
> ... and a patch implementing that would look like:
This is exactly what I meant by only update when a feature has been flagged.
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