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

[PATCH 0/2] Add --dry-run option to git-push

From
Baz <brian.ewins@gmail.com>
Date
Oct 10, 2007, 23:34 UTC
Message-ID
<2faad3050710101634s5ed39bcbn723184810bc265d5@mail.gmail.com>

Hi, there was discussion recently about the default behaviour of git-push having the potential to confuse, making it easy to push commits that are still cooking in other branches.

Its also possible for newbies to make mistakes with refspecs, but there's no way to know if you've got the syntax right without actually pushing. Steffan suggested a dry-run flag, which I've always wanted too, so here's an attempt. Patches git-send-pack, git-push, their docs, and adds a test for git-push.

Treat me gentle... first patch to the list and the mailer will probably mangle it (sigh)

Cheers, Baz

Diffstat:
 Documentation/git-push.txt      |    6 +++++-
 Documentation/git-send-pack.txt |    5 ++++-
 builtin-push.c                  |   10 ++++++++--
 send-pack.c                     |   31 +++++++++++++++++++------------
 t/t5516-fetch-push.sh           |   10 ++++++++++
 5 files changed, 46 insertions(+), 16 deletions(-)
Next: Lars Hjemli
Message 1 of 5 in “Add --dry-run option to git-push”
  1. 0/2 Add --dry-run option to git-pushBaz, Oct 10, 2007
  2. Lars HjemliOct 11, 2007
  3. 1/2 Add a --dry-run option to git-send-pack.Brian Ewins, Oct 11, 2007
  4. 2/2 Add a --dry-run option to git-push.Brian Ewins, Oct 11, 2007
  5. Lars HjemliOct 11, 2007

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.