git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Christopher Head <bugs@chead.ca>, git@vger.kernel.org
Subject: Re: Push force-with-lease with multi-URL remote
Date: Mon, 29 Jul 2019 14:44:00 -0700	[thread overview]
Message-ID: <xmqqwog0tt27.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190729192040.GD14943@sigill.intra.peff.net> (Jeff King's message of "Mon, 29 Jul 2019 15:20:40 -0400")

Jeff King <peff@peff.net> writes:

> Yeah, the auto-update of the tracking refs came later (so I think you
> could argue the bad interaction is my fault!).

Heh, I somehow thought it was somebody else.

> Hmm, true. I'd almost argue that --force-with-lease, at least in its
> default mode with no explicit lease source specified, should allow an
> update from X to Y to be a successful noop if the remote "somehow"
> already moved to Y.

I've already written the --force-with-lease that expects what you
have on your remote-tracking branch off as a gross misdesign that
should be deprecated in the longer term; I do not have a strong
opinion on the tweaks to be done to the feature until it gets
dropped ;-)


  reply	other threads:[~2019-07-29 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 16:54 Push force-with-lease with multi-URL remote Christopher Head
2019-07-27 17:46 ` Junio C Hamano
2019-07-27 18:15   ` Christopher Head
2019-07-27 20:57     ` Junio C Hamano
2019-07-27 21:43       ` Christopher Head
2019-07-29  5:19         ` Junio C Hamano
2019-07-29 10:20 ` Jeff King
2019-07-29 13:33   ` Junio C Hamano
2019-07-29 13:47     ` Christopher Head
2019-07-29 19:20     ` Jeff King
2019-07-29 21:44       ` Junio C Hamano [this message]
2019-07-29 22:29         ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqwog0tt27.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=bugs@chead.ca \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).