From: Michael Haggerty <mhagger@alum.mit.edu>
To: sandy2010 <sandeeptt@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Migration from CVS to GIT - Multiple directories in CVS repo to a single Git repo
Date: Wed, 22 Jun 2011 12:58:29 +0200 [thread overview]
Message-ID: <4E01CAD5.8080808@alum.mit.edu> (raw)
In-Reply-To: <1308733591425-6503493.post@n2.nabble.com>
On 06/22/2011 11:06 AM, sandy2010 wrote:
> I'm aware of cvs2git and git fast-import utilities to do this. My
> requirement is little different.
> My CVS Repo is:
> /cvs/BFARM
>
> This consists of following directories:
> Misc/suite1
> Misc/suite2
> Misc/suite3
>
> Now, I want to Migrate the suite1 and suite2 into a single Git repo
> "/git/Testsuites" and it should look like this:
> /git/Testsuites/suite1
> /git/Testsuites/suite2
>
> How can I do this? I do not want to make suite1 and suite2 as separate git
> repos.
Since CVS works filewise, you can simply move the suite1 and suite2
directories from within the CVS repository into a pseudo CVS repository,
then convert that:
$ mkdir /tmp/fake-cvs-repo /tmp/fake-cvs-repo/Misc
$ cp -pr /cvs/BFARM/CVSROOT /tmp/fake-cvs-repo
$ cp -pr /cvs/BFARM/Misc/suite1 /tmp/fake-cvs-repo/Misc
$ cp -pr /cvs/BFARM/Misc/suite2 /tmp/fake-cvs-repo/Misc
and then convert the pseudo-repository "/tmp/fake-cvs-repo/Misc".
Depending on the tools and filesystems involved, you might be able to
use hardlinks or symlinks instead of full copies when building up the
pseudorepo.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-06-22 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 9:06 Migration from CVS to GIT - Multiple directories in CVS repo to a single Git repo sandy2010
2011-06-22 9:22 ` Andreas Ericsson
2011-06-22 10:21 ` sandy2010
2011-06-22 11:55 ` Andreas Ericsson
2011-06-22 10:58 ` Michael Haggerty [this message]
2011-06-23 5:58 ` sandy2010
2011-06-23 8:11 ` Comparison of CVS and Git (was: Re: Migration from CVS to GIT) Jakub Narebski
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=4E01CAD5.8080808@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=sandeeptt@yahoo.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).