From: Stephan Beyer <s-beyer@gmx.net>
To: git@vger.kernel.org
Cc: Stephan Beyer <s-beyer@gmx.net>,
Daniel Barkalow <barkalow@iabervon.org>,
Christian Couder <chriscool@tuxfamily.org>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Sequencer migration patches
Date: Wed, 16 Jul 2008 22:45:19 +0200 [thread overview]
Message-ID: <cover.1216233918.git.s-beyer@gmx.net> (raw)
In-Reply-To: <fd9b4f2b04c9b997c6bdba90352eb1ef973114ae.1216233915.git.s-beyer@gmx.net>
Hi,
the following patches migrate git-am and git-rebase--interactive to
git-sequencer.
But there are some issues I want to mention.
I've compared performance of original rebase and am with the
sequencer-based ones and the sequencer-based ones perform fairly bad.
For example, applying 45 patches with git-am took 3 seconds using the
original and 8 seconds using the sequencer-based one.
Rebasing 100 commits takes 10.1 seconds instead of only 4.8 seconds
on my test machine.
I expect that the builtin-sequencer performs muuuch better.
But as long as there is no builtin-sequencer these patches should
perhaps not be applied.
Well, I could offer to provide patches to put sequencer-based git-am and
git-rebase-i scripts to contrib/examples/ (or contrib/sequencer-examples/
or something else). ;-)
Regards,
Stephan
Stephan Beyer (2):
Migrate git-am to use git-sequencer
Introduce git am --abort
Documentation/git-am.txt | 5 +-
Documentation/git-rerere.txt | 2 +-
contrib/completion/git-completion.bash | 2 +-
git-am.sh | 617 +++++++++++---------------------
git-rebase.sh | 7 +-
t/t4150-am.sh | 27 +-
6 files changed, 244 insertions(+), 416 deletions(-)
Stephan Beyer (1):
Migrate rebase-i to sequencer
git-rebase--interactive.sh | 438 ++++++++++-------------------------------
t/t3404-rebase-interactive.sh | 9 +-
2 files changed, 113 insertions(+), 334 deletions(-)
next prev parent reply other threads:[~2008-07-16 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 20:45 [PATCH 1/3] Add git-sequencer shell prototype Stephan Beyer
2008-07-16 20:45 ` [PATCH 2/3] Add git-sequencer documentation Stephan Beyer
2008-07-16 20:45 ` [PATCH 3/3] Add git-sequencer test suite (t3350) Stephan Beyer
2008-07-16 20:45 ` Stephan Beyer [this message]
2008-07-16 20:45 ` [PATCH 1/2] Migrate git-am to use git-sequencer Stephan Beyer
2008-07-16 20:45 ` [PATCH 2/2] Introduce git am --abort Stephan Beyer
2008-07-16 20:45 ` [PATCH] Migrate rebase-i to sequencer Stephan Beyer
2008-07-17 13:05 ` Sequencer migration patches Stephan Beyer
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.1216233918.git.s-beyer@gmx.net \
--to=s-beyer@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.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).