From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Felipe Contreras <felipe.contreras@gmail•com>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [RFC/PATCH] git-remote-mediawiki: reset private ref after non-dumb push
Date: Tue, 27 Aug 2013 09:25:27 +0200 [thread overview]
Message-ID: <vpqsixvfvdk.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAMP44s1dNHi5Xg9KPp_717BMfAem-H8YOv5c+K9-2b-Aewpe3w@mail.gmail.com> (Felipe Contreras's message of "Mon, 26 Aug 2013 11:28:02 -0500")
Felipe Contreras <felipe.contreras@gmail•com> writes:
> On Mon, Aug 26, 2013 at 4:16 AM, Matthieu Moy
> <Matthieu.Moy@grenoble-inp•fr> wrote:
>> Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:
>>
>>> Junio C Hamano <gitster@pobox•com> writes:
>>>
>>>> Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:
>>>
>>> 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.
OK, I didn't understand you meant patching Git itself for that. So it
makes sense to turn my toy patch into a real patch I guess. Any comment
on the capability name? I used dont-update-private, which is a bit long.
The actual precise name would be dont-update-private-for-push, but
that's really long. Any better idea?
Just to be sure: you originally wrote "update the remote namespace only
when a certain feature has been flagged". My patch differs in two ways:
it's opt-out, not opt-in, and it's about updating the _private_
namespace, not the remote. Any comment on what's the best behavior?
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-08-27 7:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:31 [RFC/PATCH] git-remote-mediawiki: reset private ref after non-dumb push Matthieu Moy
2013-08-21 19:48 ` Felipe Contreras
2013-08-21 21:36 ` Matthieu Moy
2013-08-22 17:20 ` Felipe Contreras
2013-08-23 8:25 ` Matthieu Moy
2013-08-23 19:52 ` Felipe Contreras
2013-08-24 7:46 ` Matthieu Moy
2013-08-25 3:50 ` Junio C Hamano
2013-08-26 8:48 ` Matthieu Moy
2013-08-26 9:16 ` Matthieu Moy
2013-08-26 16:28 ` Felipe Contreras
2013-08-27 7:25 ` Matthieu Moy [this message]
2013-08-29 18:58 ` [PATCH 1/4] git-remote-mediawiki: add test and check Makefile targets Matthieu Moy
2013-08-29 18:58 ` [PATCH 2/4] transport-helper: add dont-update-private capability Matthieu Moy
2013-08-29 19:14 ` Felipe Contreras
2013-09-02 7:19 ` [PATCH v2 1/4] git-remote-mediawiki: add test and check Makefile targets Matthieu Moy
2013-09-02 7:19 ` [PATCH v2 2/4] transport-helper: add no-private-update capability Matthieu Moy
2013-09-02 7:28 ` Felipe Contreras
2013-09-02 7:41 ` [PATCH v3 2/4] transport-helper: add dont-update-private capability Matthieu Moy
2013-09-03 15:45 ` [PATCH v4 2/4] transport-helper: add no-private-update capability Matthieu Moy
2013-09-02 7:19 ` [PATCH v2 3/4] git-remote-mediawiki: use no-private-update capability on dumb push Matthieu Moy
2013-09-02 7:19 ` [PATCH v2 4/4] git-remote-mediawiki: no need to update private ref in non-dumb push Matthieu Moy
2013-08-29 18:58 ` [PATCH 3/4] git-remote-mediawiki: use dont-update-private capability on dumb push Matthieu Moy
2013-08-29 19:08 ` Junio C Hamano
2013-08-29 18:58 ` [PATCH 4/4] git-remote-mediawiki: no need to update private ref in non-dumb push Matthieu Moy
2013-08-29 19:09 ` Junio C Hamano
2013-08-26 16:26 ` [RFC/PATCH] git-remote-mediawiki: reset private ref after " Junio C Hamano
2013-08-27 7:28 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqsixvfvdk.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=felipe.contreras@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox