From: Wink Saville <wink@saville.com>
To: git@vger.kernel.org
Cc: Wink Saville <wink@saville.com>,
sunshine@sunshineco.com, Johannes.Schindelin@gmx.de
Subject: [RFC PATCH v2 0/1] rebase-interactive: Add git_rebase__interactive__preserve_merges
Date: Wed, 21 Mar 2018 10:44:37 -0700 [thread overview]
Message-ID: <cover.1521653702.git.wink@saville.com> (raw)
In-Reply-To: <CAPig+cSm3kHF_hTRKutCCNsY82sE3xZfXJkQsKi+zedq9rdnPw@mail.gmail.com>
Version 2 keeps all changes in git-rebase--interactive.sh this should
make it easier to use blame. But there is quite a bit of refactoring
and reformatting so using "git blame -w" or "git blame -w -C -C" is
needed to improve the results of blame.
I can break this into several patches to have the history show the code
movement more directly if that is desired.
Wink Saville (1):
rebase-interactive: Add git_rebase__interactive__preserve_merges
git-rebase--interactive.sh | 469 +++++++++++++++++++++++++--------------------
git-rebase.sh | 16 +-
2 files changed, 273 insertions(+), 212 deletions(-)
--
2.16.2
next prev parent reply other threads:[~2018-03-21 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 20:45 [RFC PATCH 0/3] rebase-interactive Wink Saville
2018-03-20 20:45 ` [RFC PATCH 1/3] rebase-interactive: create git-rebase--interactive--lib.sh Wink Saville
2018-03-20 20:45 ` [RFC PATCH 2/3] rebase-interactive: create git-rebase--interactive--preserve-merges Wink Saville
2018-03-20 20:45 ` [RFC PATCH 3/3] rebase-interactive: refactor git-rebase--interactive to use library Wink Saville
2018-03-20 21:11 ` [RFC PATCH 0/3] rebase-interactive Eric Sunshine
2018-03-20 21:23 ` Wink Saville
2018-03-20 21:47 ` Eric Sunshine
2018-03-21 3:31 ` Wink Saville
2018-03-21 8:54 ` Eric Sunshine
2018-03-21 17:44 ` Wink Saville [this message]
2018-03-21 17:44 ` [RFC PATCH v2 1/1] rebase-interactive: Add git_rebase__interactive__preserve_merges Wink Saville
2018-03-21 19:42 ` Junio C Hamano
2018-03-21 21:49 ` Wink Saville
2018-03-21 22:43 ` Junio C Hamano
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=cover.1521653702.git.wink@saville.com \
--to=wink@saville.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.