summaryrefslogtreecommitdiff
path: root/Documentation/cvs-migration.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-08-30 20:51:01 (GMT)
committerJunio C Hamano <junkio@cox.net>2005-08-30 20:55:34 (GMT)
commit8db9307c9ca143fedaa972236054a5783c40bd37 (patch)
tree714f245e49ec7229a4ba7aff2bc396db6f1f5140 /Documentation/cvs-migration.txt
parentcc9f24d024e7e4bf0b2fbd4e1beb7eb1a425805f (diff)
downloadgit-8db9307c9ca143fedaa972236054a5783c40bd37.zip
git-8db9307c9ca143fedaa972236054a5783c40bd37.tar.gz
git-8db9307c9ca143fedaa972236054a5783c40bd37.tar.bz2
Documentaion updates.
Mostly making the formatted html prettier. Signed-off-by: Junio C Hamano <junkio@cox.net> (cherry picked from 7adf1f15ebe074d4767df941817a6cf86d8e2533 commit)
Diffstat (limited to 'Documentation/cvs-migration.txt')
-rw-r--r--Documentation/cvs-migration.txt20
1 files changed, 11 insertions, 9 deletions
diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt
index 8db1409..6e48bde 100644
--- a/Documentation/cvs-migration.txt
+++ b/Documentation/cvs-migration.txt
@@ -1,5 +1,6 @@
Git for CVS users
=================
+v0.99.5, Aug 2005
Ok, so you're a CVS user. That's ok, it's a treatable condition, and the
first step to recovery is admitting you have a problem. The fact that
@@ -8,12 +9,12 @@ already.
The thing about CVS is that it absolutely sucks as a source control
manager, and you'll thus be happy with almost anything else. Git,
-however, may be a bit _too_ different (read: "good") for your taste, and
+however, may be a bit 'too' different (read: "good") for your taste, and
does a lot of things differently.
One particular suckage of CVS is very hard to work around: CVS is
-basically a tool for tracking _file_ history, while git is a tool for
-tracking _project_ history. This sometimes causes problems if you are
+basically a tool for tracking 'file' history, while git is a tool for
+tracking 'project' history. This sometimes causes problems if you are
used to doing very strange things in CVS, in particular if you're doing
things like making branches of just a subset of the project. Git can't
track that, since git never tracks things on the level of an individual
@@ -22,17 +23,18 @@ file, only on the whole project level.
The good news is that most people don't do that, and in fact most sane
people think it's a bug in CVS that makes it tag (and check in changes)
one file at a time. So most projects you'll ever see will use CVS
-_as_if_ it was sane. In which case you'll find it very easy indeed to
+'as if' it was sane. In which case you'll find it very easy indeed to
move over to Git.
-First off: this is not a git tutorial. See Documentation/tutorial.txt
-for how git actually works. This is more of a random collection of
-gotcha's and notes on converting from CVS to git.
+First off: this is not a git tutorial. See
+link:tutorial.html[Documentation/tutorial.txt] for how git
+actually works. This is more of a random collection of gotcha's
+and notes on converting from CVS to git.
Second: CVS has the notion of a "repository" as opposed to the thing
that you're actually working in (your working directory, or your
"checked out tree"). Git does not have that notion at all, and all git
-working directories _are_ the repositories. However, you can easily
+working directories 'are' the repositories. However, you can easily
emulate the CVS model by having one special "global repository", which
people can synchronize with. See details later, but in the meantime
just keep in mind that with git, every checked out working tree will
@@ -55,7 +57,7 @@ will need the help of a program called "cvsps":
which is not actually related to git at all, but which makes CVS usage
look almost sane (ie you almost certainly want to have it even if you
-decide to stay with CVS). However, git will want at _least_ version 2.1
+decide to stay with CVS). However, git will want 'at least' version 2.1
of cvsps (available at the address above), and in fact will currently
refuse to work with anything else.