From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: git@vger.kernel.org
Cc: Nicolas Vigier <boklm@mars-attacks.org>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v4 6/9] rebase: don't try to match -M option
Date: Mon, 10 Feb 2014 01:03:35 +0000 [thread overview]
Message-ID: <1391994218-639101-7-git-send-email-sandals@crustytoothpaste.net> (raw)
In-Reply-To: <1391994218-639101-1-git-send-email-sandals@crustytoothpaste.net>
From: Nicolas Vigier <boklm@mars-attacks.org>
The -M option does not exist in OPTIONS_SPEC, so there is no use to try
to find it.
Signed-off-by: Nicolas Vigier <boklm@mars-attacks.org>
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
---
git-rebase.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-rebase.sh b/git-rebase.sh
index d1835ba..3b55211 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -267,7 +267,7 @@ do
--no-fork-point)
fork_point=
;;
- -M|-m)
+ -m)
do_merge=t
;;
-X)
--
1.9.0.rc3.1008.gd08b47c.dirty
next prev parent reply other threads:[~2014-02-10 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 1:03 [PATCH v4 0/9] add --gpg-sign to rebase and pull brian m. carlson
2014-02-10 1:03 ` [PATCH v4 1/9] cherry-pick, revert: add the --gpg-sign option brian m. carlson
2014-02-10 1:03 ` [PATCH v4 2/9] git-sh-setup.sh: add variable to use the stuck-long mode brian m. carlson
2014-02-10 1:03 ` [PATCH v4 3/9] am: parse options in " brian m. carlson
2014-02-10 1:03 ` [PATCH v4 4/9] am: add the --gpg-sign option brian m. carlson
2014-02-10 1:03 ` [PATCH v4 5/9] rebase: remove useless arguments check brian m. carlson
2014-02-10 1:03 ` brian m. carlson [this message]
2014-02-10 1:03 ` [PATCH v4 7/9] rebase: parse options in stuck-long mode brian m. carlson
2014-02-10 6:59 ` Eric Sunshine
2014-02-11 0:32 ` brian m. carlson
2014-02-10 1:03 ` [PATCH v4 8/9] rebase: add the --gpg-sign option brian m. carlson
2014-02-10 1:03 ` [PATCH v4 9/9] pull: " brian m. carlson
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=1391994218-639101-7-git-send-email-sandals@crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=boklm@mars-attacks.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).