All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
	Richard Hansen <rhansen@bbn.com>
Subject: Re: [PATCH v5 03/10] transport-helper: add 'force' to 'export' helpers
Date: Fri, 01 Nov 2013 09:35:52 -0700	[thread overview]
Message-ID: <xmqqa9ho2i6v.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAMP44s1wfk3zmiof6E474vNi72zTo_QFj=56G3POjopukGK-5Q@mail.gmail.com> (Felipe Contreras's message of "Fri, 1 Nov 2013 09:37:14 -0600")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> On Fri, Nov 1, 2013 at 8:49 AM, Junio C Hamano <gitster@pobox.com> wrote:
>
>> Because updated helpers know 'force' option, such a s/die/warning/
>> change would not affect them at all.
>
> Yeah, that makes sense.

OK, then let's queue this separately on top, so that we can revert
it more easily when our "s/die/warning/ should be safe and more
friendly to existing users" reasoning we discussed is found to be
faulty later.

-- >8 --
Subject: [PATCH] transport-helper: demote lack of "force" option to a warning

It would have been a good conservative position to take, if there
were no existing helpers, to die when the user asked to force a push
through a transport helper mechanism and the helper script hasn't
been updated to handle the "force" option.

There however are existing helpers in the field and none of them
obviously has been taught about the option yet.  If a helper has not
been updated to understand "force", but the user has happily been
accepting the result of "git push $there +master" (perhaps because
he has never pushed a non-ff history so far), the change made
previously in this series will fail the push, which would be a minor
regression for such a user.

Demote lack of "force" option from a "die()" to a "warning()".  By
doing so, such a user now gets a warning that notifies him that his
push has been working by accident, even when the particular ff-push
that showed the error message goes through successfully.

If his push does need "force", he gets the same old behaviour,
possibly a broken one, out of the helper that has not been update,
but again he does see the warning.

Helped-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 transport-helper.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/transport-helper.c b/transport-helper.c
index ef91882..6b167ea 100644
--- a/transport-helper.c
+++ b/transport-helper.c
@@ -862,7 +862,7 @@ static int push_refs_with_export(struct transport *transport,
 
 	if (flags & TRANSPORT_PUSH_FORCE) {
 		if (set_helper_option(transport, "force", "true") != 0)
-			die("helper %s does not support 'force'", data->name);
+			warning("helper %s does not support 'force'", data->name);
 	}
 
 	helper = get_helper(transport);
-- 
1.8.5-rc0-205-g5b7460b

  reply	other threads:[~2013-11-01 16:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  9:36 [PATCH v5 10/10] transport-helper: add support to delete branches Felipe Contreras
2013-10-31  9:36 ` [PATCH v5 00/10] transport-helper: updates Felipe Contreras
2013-10-31 17:59   ` Max Horn
2013-10-31 18:10     ` Junio C Hamano
2013-10-31 18:30       ` Felipe Contreras
2013-10-31 18:34       ` Junio C Hamano
2013-10-31 18:41       ` Max Horn
2013-11-11  5:09   ` [PATCH v5 11/10] test-hg.sh: tests are now expected to pass Richard Hansen
2013-11-11  5:10   ` [PATCH v5 12/10] remote-bzr: support the new 'force' option Richard Hansen
2013-11-11 11:51     ` Felipe Contreras
2013-11-11 18:12       ` Richard Hansen
2013-11-11 18:15         ` Felipe Contreras
2013-10-31  9:36 ` [PATCH v5 01/10] transport-helper: fix extra lines Felipe Contreras
2013-10-31 18:16   ` Junio C Hamano
2013-10-31  9:36 ` [PATCH v5 08/10] fast-import: add support to delete refs Felipe Contreras
2013-10-31 18:41   ` Max Horn
2013-10-31  9:36 ` [PATCH v5 05/10] fast-export: improve argument parsing Felipe Contreras
2013-10-31  9:36 ` [PATCH v5 06/10] fast-export: add new --refspec option Felipe Contreras
2013-10-31 18:26   ` Junio C Hamano
2013-10-31 18:41     ` Felipe Contreras
2013-11-06 21:00       ` Junio C Hamano
2013-11-06 22:14         ` Jeff King
2013-11-06 22:31           ` Junio C Hamano
2013-11-06 22:41             ` Junio C Hamano
2013-11-08 23:44           ` Junio C Hamano
2013-11-09  0:06             ` Jeff King
2013-11-07  1:00         ` Felipe Contreras
2013-10-31  9:36 ` [PATCH v5 03/10] transport-helper: add 'force' to 'export' helpers Felipe Contreras
2013-10-31 18:21   ` Junio C Hamano
2013-10-31 18:55     ` Felipe Contreras
2013-10-31 19:07       ` Junio C Hamano
2013-11-01 14:49         ` Junio C Hamano
2013-11-01 15:37           ` Felipe Contreras
2013-11-01 16:35             ` Junio C Hamano [this message]
2013-11-01 17:28               ` Eric Sunshine
2013-11-11  5:01   ` [PATCH] fixup! " Richard Hansen
2013-10-31  9:36 ` [PATCH v5 09/10] fast-export: add support to delete refs Felipe Contreras
2013-10-31 19:29   ` Max Horn
2013-10-31 19:41     ` Felipe Contreras
2013-10-31 19:47       ` Max Horn
2013-10-31 19:53         ` Felipe Contreras
2013-10-31 22:38           ` Max Horn
2013-10-31  9:36 ` [PATCH v5 07/10] transport-helper: add support for old:new refspec Felipe Contreras
2013-10-31  9:36 ` [PATCH v5 04/10] transport-helper: check for 'forced update' message Felipe Contreras
2013-10-31  9:36 ` [PATCH v5 02/10] transport-helper: don't update refs in dry-run Felipe Contreras

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=xmqqa9ho2i6v.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=rhansen@bbn.com \
    --cc=srabbelier@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.