From: Phil Hord <hordp@cisco.com>
To: Greg Price <price@MIT.EDU>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 4/6] rebase: --rewrite-{refs,heads,tags} to pull refs along with branch
Date: Mon, 27 Jun 2011 12:11:39 -0400 [thread overview]
Message-ID: <4E08ABBB.9060009@cisco.com> (raw)
In-Reply-To: <c2d11ffe876a540b6fad46e2ecc57a24018cfb73.1309133817.git.greg@quora.com>
On 11/18/2009 06:51 PM, Greg Price wrote:
> diff --git a/git-rebase.sh b/git-rebase.sh
> index 1bfe6a8..7c365ab 100755
> --- a/git-rebase.sh
> +++ b/git-rebase.sh
> @@ -38,6 +38,9 @@ git-rebase [-i] --continue | --abort | --skip
> v,verbose! display a diffstat of what changed upstream
> q,quiet! be quiet. implies --no-stat
> onto=! rebase onto given branch instead of upstream
> +rewrite-heads! rewrite intermediate heads on branch
> +rewrite-tags! rewrite intermediate tags on branch
> +rewrite-refs=! rewrite intermediate refs matching pattern
> p,preserve-merges! try to recreate merges instead of ignoring them
> s,strategy=! use the given merge strategy
> no-ff! cherry-pick all commits, even if unchanged
> @@ -96,6 +99,7 @@ state_dir=
> # One of {'', continue, skip, abort}, as parsed from command line
> action=
> preserve_merges=
> +rebase_refs=
> autosquash=
> test "$(git config --bool rebase.autosquash)" = "true" && autosquash=t
I think you meant to spell that "rewrite_refs=" instead of "rebase_refs=".
>
> @@ -246,6 +250,19 @@ do
> strategy="$1"
> do_merge=t
> ;;
> + --rewrite-refs)
> + shift
> + rewrite_refs="$rewrite_refs $1"
> + test -z "$interactive_rebase" && interactive_rebase=implied
> + ;;
> + --rewrite-heads)
> + rewrite_refs="$rewrite_refs refs/heads"
> + test -z "$interactive_rebase" && interactive_rebase=implied
> + ;;
> + --rewrite-tags)
> + rewrite_refs="$rewrite_refs refs/tags"
> + test -z "$interactive_rebase" && interactive_rebase=implied
> + ;;
> -n)
> diffstat=
> ;;
Then it matches the rest of the commit.
Phil
next prev parent reply other threads:[~2011-06-27 16:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 0:16 [PATCH 0/6] rebase: command "ref" and options --rewrite-{refs,heads,tags} Greg Price
2009-10-10 2:52 ` [PATCH 1/6] rebase -i: Add the "ref" command Greg Price
2011-06-27 18:46 ` Junio C Hamano
2011-06-28 11:15 ` Greg Price
2009-11-18 23:22 ` [PATCH 2/6] pretty: Add %D for script-friendly decoration Greg Price
2011-06-27 19:07 ` Junio C Hamano
2009-11-18 23:51 ` [PATCH 4/6] rebase: --rewrite-{refs,heads,tags} to pull refs along with branch Greg Price
2011-06-27 16:11 ` Phil Hord [this message]
2011-06-28 11:19 ` Greg Price
2010-01-07 23:08 ` [PATCH 3/6] for-each-ref: --stdin to match specified refs against pattern Greg Price
2010-01-25 2:26 ` [PATCH 5/6] t/lib-rebase.sh: pass through ref commands Greg Price
2010-01-25 2:28 ` [PATCH 6/6] rebase --rewrite-refs: tests Greg Price
2011-06-27 16:07 ` Phil Hord
2011-06-28 11:22 ` Greg Price
2011-06-27 21:02 ` Junio C Hamano
2011-06-28 11:20 ` Greg Price
2011-06-27 18:36 ` [PATCH 0/6] rebase: command "ref" and options --rewrite-{refs,heads,tags} Junio C Hamano
[not found] ` <BANLkTinDFYsw7-N=_Ex8i42So_0LzVAWvA@mail.gmail.com>
2011-06-28 10:47 ` Fwd: " Greg Price
2011-06-28 13:17 ` Greg Price
2011-06-30 4:25 ` Ramkumar Ramachandra
2011-08-03 13:32 ` Fwd: " Sverre Rabbelier
2011-08-03 22:31 ` Greg Price
2011-06-27 21:23 ` Junio C Hamano
[not found] ` <BANLkTi=Akib+7R7D2GEwV8dOTQ1vsqgfxA@mail.gmail.com>
2011-06-28 10:56 ` Fwd: " Greg Price
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=4E08ABBB.9060009@cisco.com \
--to=hordp@cisco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=price@MIT.EDU \
/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).