From: Jakub Narebski <jnareb@gmail.com>
To: sandy2010 <sandeeptt@yahoo.com>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Comparison of CVS and Git (was: Re: Migration from CVS to GIT)
Date: Thu, 23 Jun 2011 01:11:59 -0700 (PDT) [thread overview]
Message-ID: <m3mxh955nm.fsf_-_@localhost.localdomain> (raw)
In-Reply-To: <1308808706969-6507269.post@n2.nabble.com>
sandy2010 <sandeeptt@yahoo.com> writes:
> 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?
A bit of self-promotion:
"Difference between GIT and CVS" on StackOverflow (my answer)
http://stackoverflow.com/questions/802573/difference-between-git-and-cvs/824241#824241
A blog post I recently found, describing how the workflow changed
rather that the differences between Git and CVS:
"From CVS to Git, 9 Things I\u2019ve Learned" on EclipseSource blog
http://eclipsesource.com/blogs/2011/06/09/git-lessons-learned/
This article describes how Git could came into being, IMHO quite well
presenting Git philosophy as well:
"The Git Parable" by Tom Preston-Werner (of GitHub)
http://tom.preston-werner.com/2009/05/19/the-git-parable.html
And just FYI, another tool to convert CVS to Git (non-incremental):
http://cvs2svn.tigris.org/cvs2git.html
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2011-06-23 8:12 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
2011-06-23 8:11 ` Jakub Narebski [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=m3mxh955nm.fsf_-_@localhost.localdomain \
--to=jnareb@gmail.com \
--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).