From: Andreas Ericsson <ae@op5.se>
To: Adam Mercer <ramercer@gmail.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: files missing after converting a cvs repository to git
Date: Wed, 08 Oct 2008 08:16:56 +0200 [thread overview]
Message-ID: <48EC5058.5020509@op5.se> (raw)
In-Reply-To: <799406d60810070855y53cf5191m111ce8f5380f96c6@mail.gmail.com>
Adam Mercer wrote:
> On Tue, Oct 7, 2008 at 01:08, Andreas Ericsson <ae@op5.se> wrote:
>
>> Has the CVS repo been tampered with in the past? If so, it's entirely
>> possible that checking out and working with CVS works just fine, but
>> getting history into coherent changesets is impossible.
>
> Unfortunately yes. Thats what I thought, and was afraid, was going on.
> I've managed to get things working by restoring some of the missing
> files ,v files from a backup and regenerating the tracking
> repositories. Then I had to remove the files in question from cvs and
> readd them, git cvsimport then saw these files.
>
Ouch. In that case, all bets are off when it comes to correctly cloning
the history, I'm afraid. On the up-side, if you get a oneshot conversion
done properly you can easily convert it to something else later in case
git doesn't meet your needs, and it might even be easier to add commit
support to "git cvsserver" than it is to fix your broken repository
(it might be in there already; I don't use it so I don't know), in
which case you can use CVS with a git object store.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2008-10-08 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 22:02 files missing after converting a cvs repository to git Adam Mercer
2008-10-07 6:08 ` Andreas Ericsson
2008-10-07 10:15 ` Jakub Narebski
2008-10-07 10:46 ` Michael Haggerty
2008-10-07 15:58 ` Adam Mercer
2008-10-07 15:55 ` Adam Mercer
2008-10-08 6:16 ` Andreas Ericsson [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=48EC5058.5020509@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=ramercer@gmail.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).