|
Size: 625
Comment:
|
Size: 409
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == 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 | |
Ernest is his name and believes it sounds often good. Some period of time ago he chose to stay in Idaho.<<BR>> What he really enjoys doing is jumping in but he's been running into new things lately. The job he's been occupying for a few years is a procurement police but his promotion you should not comes. Go to his website to find outside more: http://www.impedanceanalyzer.com.au/news_feed.php?itemid=16 |
Ernest is his name and believes it sounds often good. Some period of time ago he chose to stay in Idaho.
What he really enjoys doing is jumping in but he's been running into new things lately. The job he's been occupying for a few years is a procurement police but his promotion you should not comes. Go to his website to find outside more: http://www.impedanceanalyzer.com.au/news_feed.php?itemid=16