Re: [RFC/PATCH] git-remote-mediawiki: reset private ref after non-dumb push
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Aug 26, 2013, 16:28 UTC
- Message-ID
- <CAMP44s1dNHi5Xg9KPp_717BMfAem-H8YOv5c+K9-2b-Aewpe3w@mail.gmail.com>
- In-Reply-To
- <vpqr4dgizhm.fsf@anie.imag.fr>
On Mon, Aug 26, 2013 at 4:16 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 27 quoted lines
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes: > >> Junio C Hamano <gitster@pobox.com> writes: >> >>> Matthieu Moy <Matthieu.Moy@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.
-- Felipe Contreras