From: sandy2010 <sandeeptt@yahoo.com>
To: 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 22:58:26 -0700 (PDT) [thread overview]
Message-ID: <1308808706969-6507269.post@n2.nabble.com> (raw)
In-Reply-To: <4E01CAD5.8080808@alum.mit.edu>
Thanks Michael! This worked like a charm! I was not aware that we can do such
things in CVS. Can you point me to some good docs/articles on such
comparison of CVS and Git?
Thanks again!
--
View this message in context: http://git.661346.n2.nabble.com/Migration-from-CVS-to-GIT-Multiple-directories-in-CVS-repo-to-a-single-Git-repo-tp6503493p6507269.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2011-06-23 5: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
2011-06-23 5:58 ` sandy2010 [this message]
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=1308808706969-6507269.post@n2.nabble.com \
--to=sandeeptt@yahoo.com \
--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).