From: Christoph Hellwig <hch@lst.de>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Matthias Urlichs <smurf@smurf.noris.de>, git@vger.kernel.org
Subject: Re: git-cvsimport fuzzy commit log matching?
Date: Tue, 23 Dec 2008 16:16:43 +0100 [thread overview]
Message-ID: <20081223151643.GA18657@lst.de> (raw)
In-Reply-To: <46a038f90812230453m4122e018l2cc22be3f40ab630@mail.gmail.com>
On Tue, Dec 23, 2008 at 10:53:42AM -0200, Martin Langhoff wrote:
> What you could do is
>
> 1 - run cvsps with export to a file (I've posted in this list how to
> run it exactly as cvsimport does)
> 2 - post-process cvsps ouput with perl (there's a parser already in
> cvsimport ;-) )
> 3 - run cvsimport with the post-processed file
>
> Or postprocess the imported git tree as others have suggested.
Instead of post-processing I hacked cvsps. It already has a different
way to detect changesets when running in --bkcvs mode, and re-using that
one for ptools works great.
prev parent reply other threads:[~2008-12-23 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 11:03 git-cvsimport fuzzy commit log matching? Christoph Hellwig
2008-12-23 11:06 ` Pierre Habouzit
2008-12-23 12:53 ` Martin Langhoff
2008-12-23 15:16 ` Christoph Hellwig [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=20081223151643.GA18657@lst.de \
--to=hch@lst.de \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=smurf@smurf.noris.de \
/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.