From: martin.von.zweigbergk@gmail.com
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH 0/5] Make git-rebase.sh more readable and easier to extend
Date: Wed, 3 Nov 2010 22:09:35 +0100 [thread overview]
Message-ID: <1288818580-7576-1-git-send-email-martin.von.zweigbergk@gmail.com> (raw)
This is my first patch set to mail to this list, so I hope I get things right...
This patch set tries to make git-rebase.sh a bit more readable and to make it a
bit easier to extend. The only change in behavior that I know I have introduced
(in PATCH 2) is that "git rebase (--continue | --skip)" when an empty
"$GIT_DIR/rebase-merge" exists now gives slightly fewer error messages while
trying to cat files in that directory. The only reason for this change was to
make it better aligned with the behavior when an empty
"$GIT_DIR/rebase-apply" exists.
These patches are related to, but different from, the mail I sent about
extracting common code between git-rebase.sh and git-rebase--interactive.sh (see
http://thread.gmane.org/gmane.comp.version-control.git/160517). I would like to
base that work on the current patch set.
git-rebase.sh | 148 +++++++++++++++++++++++++--------------------------------
1 files changed, 65 insertions(+), 83 deletions(-)
next reply other threads:[~2010-11-04 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:09 martin.von.zweigbergk [this message]
2010-11-03 21:09 ` [PATCH 1/5] rebase: clearer names for directory variables martin.von.zweigbergk
2010-11-03 21:09 ` [PATCH 2/5] rebase: refactor reading of state martin.von.zweigbergk
2010-11-03 21:09 ` [PATCH 3/5] rebase: read state outside loop martin.von.zweigbergk
2010-11-03 21:09 ` [PATCH 4/5] rebase: remove unused rebase state 'prev_head' martin.von.zweigbergk
2010-11-03 21:09 ` [PATCH 5/5] rebase: read state explicitly in '--abort' martin.von.zweigbergk
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=1288818580-7576-1-git-send-email-martin.von.zweigbergk@gmail.com \
--to=martin.von.zweigbergk@gmail.com \
--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).