From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: git@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Debian TopGit maintainers <pkg-topgit@teams.debian.net>
Subject: [RFC] rerere to recreate topic branches
Date: Tue, 10 Mar 2009 10:32:00 +0100 [thread overview]
Message-ID: <20090310093200.GA12931@pengutronix.de> (raw)
Hello,
Ingo sent a similar mail some time ago[1], that's why I Cc: him.
For TopGit I want something similar as Ingo for -tip (I think): recreate
a branch with a cleaned up history but without throwing away merge
resolutions.
I think most points from Ingo's mail are already addressed. Let's see
if my mail is equally successful :-)
One step that wasn't in Ingo's list, but I consider nice is the
following workflow:
export GIT_RR_CACHE=$(mktemp -d)
git rerere add-to-cache-from origin..$branch_to_rebuild
script doing the actual rebuild
together with rerere.autocommit=true. Even though rerere is not save in
general, this workflow seems fine. I think with this approach sharing
the rr-cache isn't an issue anymore and merge conflicts that need manual
work should be quite rare, even if you do it for the first time.
I just found contrib/rerere-train.sh, which already addresses a part of
my plan.
One of my further goals is to do as much transformation without touching
the working copy (to gain speed and comfort). For that I would need git
merge to operate on an index, only and only fall back to using the
working copy if manual intervention is needed.
I have to admit that up to now I didn't look into the corresponding
code, so consider this mail (only) as starter to collect ideas and
comments.
Best regards
Uwe
[1] http://thread.gmane.org/gmane.comp.version-control.git/85176/
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2009-03-10 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 9:32 Uwe Kleine-König [this message]
2009-03-10 10:18 ` [RFC] rerere to recreate topic branches Ingo Molnar
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=20090310093200.GA12931@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pkg-topgit@teams.debian.net \
/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).