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

[PATCH 2/2] pull: document usage via OPTIONS_SPEC

From
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 23, 2008, 00:52 UTC
Message-ID
<1203727950-14980-2-git-send-email-jaysoffian@gmail.com>
In-Reply-To
<1203727950-14980-1-git-send-email-jaysoffian@gmail.com>
document usage via OPTIONS_SPEC
Signed-off-by: Jay Soffian <jaysoffian@gmail.com>
---
 git-pull.sh |   32 +++++++++++++++++++++++++++++---
 1 files changed, 29 insertions(+), 3 deletions(-)
diff --git a/git-pull.sh b/git-pull.sh
index 3ce32b5..194c1d0 100755
--- a/git-pull.sh
+++ b/git-pull.sh
@@ -4,10 +4,36 @@
 #
 # Fetch one or more remote refs and merge it/them into the current HEAD.
 
-USAGE='[-n | --no-summary] [--[no-]commit] [--[no-]squash] [--[no-]ff] [-s strategy]... [<fetch-options>] <repo> <head>...'
-LONG_USAGE='Fetch one or more remote refs and merge it/them into the current HEAD.'
 SUBDIRECTORY_OK=Yes
-OPTIONS_SPEC=
+OPTIONS_SPEC="\
+git pull [options] [<repo>] [<refspec>]
+--
+  fetch options
+q,quiet          make the fetch process less verbose
+v,verbose        make the fetch process more verbose
+a,append         append to FETCH_HEAD instead of overwritting
+upload-pack=,    specify path to git-fetch-pack on remote end
+f,force          force local branch to be updated by remote branch
+t,tags           fetch all remote tags
+no-tags          do not fetch any remote tags
+k,keep           keep downloaded pack
+u,update-head-ok used internally between git pull and git fetch
+depth=           deep shallow history by specified number of commits
+  merge options
+summary          show diffstat at end of merge
+n,no-summary     do not show diff stat at end of merge
+commit           commit the result after merging
+no-commit        do not commit the result after merging
+squash           update the index and working tree only
+no-squash        override --squash, perform a normal merge and commit
+ff               only update branch pointer if merge is a fast-forward
+no-ff            do a merge commit even if the merge is a fast-forward
+s,strategy=      use given merge strategy
+  rebase options
+rebase           rebase after fetching
+no-rebase        merge after fetching
+s,strategy=      use given merge strategy; implies -m to rebase
+"
 . git-sh-setup
 set_reflog_action "pull $*"
 require_work_tree
-- 
1.5.4.2.285.g1e9f
Previous: Jay SoffianNext: Junio C Hamano
Message 2 of 7 in “pull: pass --strategy along to to rebase”
  1. 1/2 pull: pass --strategy along to to rebaseJay Soffian, Feb 23, 2008
  2. 2/2 pull: document usage via OPTIONS_SPECJay Soffian, Feb 23, 2008
  3. Junio C HamanoFeb 23, 2008
  4. Jay SoffianFeb 23, 2008
  5. pull: document usage via OPTIONS_SPECJay Soffian, Feb 26, 2008
  6. Junio C HamanoFeb 26, 2008
  7. Jay SoffianFeb 26, 2008

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.