|
Size: 633
Comment:
|
Size: 628
Comment: fix table formatting
|
| 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 |
| Line 10: | Line 10: |
| | '''Name''' | '''Scalability''' | '''Overhead''' | '''Description''' | | CvsLikePractice | poor | low | keep things simple, use a few central repositories | | KernelPractice | good | medium | distributed, semi-hierarchical development | |
|| '''Name''' || '''Scalability''' || '''Overhead''' || '''Description''' || || CvsLikePractice || poor || low || keep things simple, use a few central repositories || || KernelPractice || good || medium || distributed, semi-hierarchical development || |
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 |
poor |
low |
keep things simple, use a few central repositories |
|
good |
medium |
distributed, semi-hierarchical development |