From: Paul Gardiner <osronline@glidos.net>
To: git@vger.kernel.org
Subject: Re: All I wanted was git-fast-export
Date: Sat, 09 Feb 2008 22:44:47 +0000 [thread overview]
Message-ID: <47AE2CDF.4090208@glidos.net> (raw)
In-Reply-To: <alpine.LSU.1.00.0802091803580.11591@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> On Sat, 9 Feb 2008, Paul Gardiner wrote:
>
>> With your kind help, I've been able to convert a cvs repository
>> to git, but the last several years commits start with a line
>> saying "Summary;" :-( I thought it might not be hard to put
>> a filter between git-fast-export and git-fast-import to sort
>> it out.
>
> The better tool for this should be filter-branch.
filter-branch does look to be brilliant for this sort of thing,
but I don't think I can use it in my case. The git repository
in question is a mirror of a live cvs repository, which I need
to keep synced up. What I was thinking was to repeatedly do:
cvs rep => git rep => tidied git rep
using fromcvs/togit for the first step, and
git-fast-export/git-fast-import for the second. It doesn't
look to be the case that filter-branch can be used with
the source and target repositories being different, and
if I tried having one git repository that I applied
tidying to, then I don't think the syncing process would
work afterwards... or would it? Do you thing that changing
commit messages would mess up subsequent syncing? I
guess I could try it and see.
I think I need git 1.5.4 either way, and I still
haven't found a way to get that installed under SuSE 10.3
P.
next prev parent reply other threads:[~2008-02-09 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 17:27 All I wanted was git-fast-export Paul Gardiner
2008-02-09 18:04 ` Johannes Schindelin
2008-02-09 22:44 ` Paul Gardiner [this message]
2008-02-10 0:58 ` Johannes Schindelin
2008-02-10 10:07 ` Paul Gardiner
2008-02-10 12:51 ` Johannes Schindelin
2008-02-10 15:39 ` Paul Gardiner
2008-02-13 9:10 ` Paul Gardiner
2008-02-17 17:00 ` Paul Gardiner
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=47AE2CDF.4090208@glidos.net \
--to=osronline@glidos.net \
--cc=git@vger.kernel.org \
/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).