How is Mercurial different from CVS?
• “Very”. You should read and understand Mercurial basics before undertaking work with Mercurial that you care about. • In a lot of places where CVS is per-file or per-directory, Mercurial is per-repository. For example, a single Mercurial changeset may contain changes to many files throughout the tree. • With Mercurial, a complete, fully armed and operational clone of the entire Mozilla repository is on your local hard drive. Even when you are offline, you can use hg log for a list of revisions to a file or hg blame to find out who is responsible for a line of code. • You can do work locally and check it in (hg commit) without affecting anybody else. To push changes upstream, use hg push after committing. • Mercurial makes branching quick and easy and keeps merging pretty much sane. (See Publishing Mercurial Clones.) • Mercurial queues (docs) can help you juggle patches. It’s like Quilt. The idea behind Quilt is this: The scripts allow to manage a series of patches by keeping track of
• “Very”. You should read and understand Mercurial basics before undertaking work with Mercurial that you care about. • In a lot of places where CVS is per-file or per-directory, Mercurial is per-repository. For example, a single Mercurial changeset may contain changes to many files throughout the tree. • With Mercurial, a complete, fully armed and operational clone of the entire Mozilla repository is on your local hard drive. Even when you are offline, you can use hg log for a list of revisions to a file or hg blame to find out who is responsible for a line of code. • You can do work locally and check it in (hg commit) without affecting anybody else. To push changes upstream, use hg push after committing. • Mercurial makes branching quick and easy and keeps merging pretty much sane. (See Publishing Mercurial Clones.) • Mercurial queues (docs) can help you juggle patches. It’s like Quilt. The idea behind Quilt is this: The scripts allow you to manage a series of patches by keeping trac
