From: Peter Karlsson <peter@softwolves.pp.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Benoit SIGOURE <tsuna@lrde.epita.fr>, git@vger.kernel.org
Subject: Re: Recording merges after repo conversion
Date: Wed, 31 Oct 2007 13:17:13 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0710311315250.16298@ds9.cixit.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0710301504270.4362@racer.site>
Johannes Schindelin:
> No. Use filter-branch, and publish the cleaned up history (possibly as a
> new branch/repo).
I'm considering doing this, and just replace the published repository
with the "fixed" one (and fix-up all my clonings of it). I'm having
some problems digesting the git-filter-branch manual page though--is
there an easy way of automating the process, given that I now have a
"grafts" file that expresses what I would like git-filter-branch to do
(I guess it would have to work backwards changing the merge points, to
be able to find all the revisions under the names I've used in the
grafts file)?
--
\\// Peter - http://www.softwolves.pp.se/
prev parent reply other threads:[~2007-10-31 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 7:09 Recording merges after repo conversion Peter Karlsson
2007-10-09 7:19 ` Benoit SIGOURE
2007-10-30 13:34 ` Peter Karlsson
2007-10-30 14:29 ` Lars Hjemli
2007-10-30 21:06 ` Peter Karlsson
2007-10-30 21:46 ` Lars Hjemli
2007-10-31 2:28 ` Johannes Schindelin
2007-10-31 9:50 ` Peter Karlsson
2007-10-31 11:01 ` Johannes Schindelin
2007-10-31 12:07 ` Peter Karlsson
2007-10-31 12:32 ` Johannes Schindelin
2007-10-31 12:43 ` Johan Herland
2007-10-31 13:43 ` Johannes Schindelin
2007-10-31 14:37 ` Johan Herland
2007-10-31 15:03 ` Johannes Schindelin
2007-10-31 15:21 ` Johan Herland
2007-10-31 15:57 ` Johannes Schindelin
2007-10-31 16:43 ` Linus Torvalds
2007-10-31 17:08 ` Johan Herland
2007-10-30 15:05 ` Johannes Schindelin
2007-10-31 12:17 ` Peter Karlsson [this message]
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=Pine.LNX.4.64.0710311315250.16298@ds9.cixit.se \
--to=peter@softwolves.pp.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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).