|
⇤ ← Revision 1 as of 2005-08-26 00:58:35
Size: 625
Comment:
|
Size: 633
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| * How to write good ChangeSetComments * RepositoryNaming is important, because you'll probably have lots of them |
* * How to write good ChangeSetComments * * RepositoryNaming is important, because you'll probably have lots of them |
Mercurial working practices
This page documents some ways to use Mercurial. Because the software is flexible, there's no "right way", but some methods are more scalable than others.
* How to write good ChangeSetComments
* RepositoryNaming is important, because you'll probably have lots of them
Ways to collaborate
| Name | Scalability | Overhead | Description | | CvsLikePractice | poor | low | keep things simple, use a few central repositories | | KernelPractice | good | medium | distributed, semi-hierarchical development |