git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v3 0/6] "git push --cas/--lockref" renamed to "--force-with-lease"

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 23, 2013, 06:43 UTC
Message-ID
<1374561800-938-1-git-send-email-gitster@pobox.com>
This is mostly unchanged since the previous round, except that
 * The option is spelled "--force-with-lease=<ref>:<expect>".
   Nobody liked "cas" as it was too technical, many disliked
   "lockref" because "lock" sounded as if push by others were
   excluded by it while in fact this is to fail us.
   The final name implies that it is related to the "--force" that
   breaks the "must fast-forward" safety, but "with-lease" part
   conveys that there is some reservation with the forcing.  The
   observation you make before you start rebasing (or you ensure
   that everything is expendable and decide to delete) is like
   taking a lease on the ref, and as long as the lease is not
   broken by others, you can push a non-fast-forward history to
   replace what is at the remote.
 * The logic to choose default when the option is not given with an
   explicit expected value is still "the remote-tracking branch for
   the ref being updated", but the documentation warns users against
   relying on that semantics, as it was shown to be fragile during
   the discussion, and hopefully we will come up with a better and
   more robust one to replace it.

The first two preparatory patches are the same since v2. For the remainder, other than changes necessary to rename the option, the documentation part of [PATCH 3/6] has been updated to mark forms without explicit expect value as experimental.

Junio C Hamano (6):
  cache.h: move remote/connect API out of it
  builtin/push.c: use OPT_BOOL, not OPT_BOOLEAN
  remote.c: add command line option parser for "--force-with-lease"
  push --force-with-lease: implement logic to populate old_sha1_expect[]
  push --force-with-lease: tie it all together
  t5533: test "push --force-with-lease"
 Documentation/git-push.txt |  77 +++++++++++++++---
 builtin/fetch-pack.c       |   2 +
 builtin/push.c             |  19 ++++-
 builtin/receive-pack.c     |   1 +
 builtin/send-pack.c        |  26 +++++++
 cache.h                    |  62 ---------------
 connect.c                  |   1 +
 connect.h                  |  13 ++++
 fetch-pack.c               |   1 +
 fetch-pack.h               |   1 +
 refs.c                     |   8 --
 remote.c                   | 175 +++++++++++++++++++++++++++++++++++++----
 remote.h                   |  83 ++++++++++++++++++++
 send-pack.c                |   2 +
 t/t5533-push-cas.sh        | 189 +++++++++++++++++++++++++++++++++++++++++++++
 transport-helper.c         |   6 ++
 transport.c                |  13 ++++
 transport.h                |   5 ++
 upload-pack.c              |   1 +
 19 files changed, 588 insertions(+), 97 deletions(-)
 create mode 100644 connect.h
 create mode 100755 t/t5533-push-cas.sh
-- 
1.8.3.4-980-g8decd39
Next: Junio C Hamano
Message 1 of 14 in “"git push --cas/--lockref" renamed to "--force-with-lease"”
  1. 0/6 "git push --cas/--lockref" renamed to "--force-with-lease"Junio C Hamano, Jul 23, 2013
  2. 1/6 cache.h: move remote/connect API out of itJunio C Hamano, Jul 23, 2013
  3. 2/6 builtin/push.c: use OPT_BOOL, not OPT_BOOLEANJunio C Hamano, Jul 23, 2013
  4. 3/6 remote.c: add command line option parser for "--force-with-lease"Junio C Hamano, Jul 23, 2013
  5. 4/6 push --force-with-lease: implement logic to populate old_sha1_expect[]Junio C Hamano, Jul 23, 2013
  6. 5/6 push --force-with-lease: tie it all togetherJunio C Hamano, Jul 23, 2013
  7. 6/6 t5533: test "push --force-with-lease"Junio C Hamano, Jul 23, 2013
  8. Jakub NarebskiJul 23, 2013
  9. Junio C HamanoJul 23, 2013
  10. Philip OakleyJul 23, 2013
  11. Eric SunshineJul 23, 2013
  12. 7/6 t5540/5541: smart-http does not support "--force-with-lease"Junio C Hamano, Aug 1, 2013
  13. 8/6 send-pack: fix parsing of --force-with-lease optionJunio C Hamano, Aug 2, 2013
  14. 9/6 push: teach --force-with-lease to smart-http transportJunio C Hamano, Aug 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.