From: David Deller <david@horizon-nigh.org>
To: git@vger.kernel.org
Subject: [BUG] git pull does not understand --strategy-option
Date: Tue, 26 Apr 2011 10:06:36 -0400 [thread overview]
Message-ID: <BANLkTinFcob1RrOxEDDG+B6UAZGYg-smtg@mail.gmail.com> (raw)
Works using short form (-X). Works with 'git merge' using either short
or long form.
Apologies, I do not have the current version of Git, but I did not see
any mention of a related fix in changelogs.
$ git --version
git version 1.7.4.1
$ git pull --strategy=recursive --strategy-option=theirs origin master
error: unknown option `strategy-option=theirs'
usage: git fetch [<options>] [<repository> [<refspec>...]]
or: git fetch [<options>] <group>
or: git fetch --multiple [<options>] [(<repository> | <group>)...]
or: git fetch --all [<options>]
-v, --verbose be more verbose
-q, --quiet be more quiet
--all fetch from all remotes
-a, --append append to .git/FETCH_HEAD instead of overwriting
--upload-pack <PATH> path to upload pack on remote end
-f, --force force overwrite of local branch
-m, --multiple fetch from multiple remotes
-t, --tags fetch all tags and associated objects
-n do not fetch all tags (--no-tags)
-p, --prune prune remote-tracking branches no longer on remote
--recurse-submodules control recursive fetching of submodules
--dry-run dry run
-k, --keep keep downloaded pack
-u, --update-head-ok allow updating of HEAD ref
--progress force progress reporting
--depth <DEPTH> deepen history of shallow clone
$ git pull --strategy=recursive -X theirs origin master
From ssh://git.internal/repos.git
* branch master -> FETCH_HEAD
Already up-to-date.
David
next reply other threads:[~2011-04-26 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 14:06 David Deller [this message]
2011-04-27 18:27 ` [BUG] git pull does not understand --strategy-option David Deller
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=BANLkTinFcob1RrOxEDDG+B6UAZGYg-smtg@mail.gmail.com \
--to=david@horizon-nigh.org \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).