Differences between revisions 17 and 45 (spanning 28 versions)
Revision 17 as of 2009-05-14 10:18:01
Size: 2264
Editor: TorstenWill
Comment:
Revision 45 as of 2013-08-31 09:05:17
Size: 330
Editor: RenCUNW
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. These are a few tips for creating a scaleable workflow.

First, [:Merge:merge] often! This makes merging easier for everyone and you
find out about conflicts (which are often rooted in incompatible
design decisions) earlier.

Second, don't hesitate to use multiple trees locally. Mercurial makes
this fast and light-weight. Typical usage is to have an incoming tree,
an outgoing tree, and a separate tree for each area being worked on.

The incoming tree is best maintained as a pristine copy of the
upstream [:Repository:repository]. This works as a cache so that you don't have to
[:Pull:pull] multiple copies over the network. No need to check files out here
as you won't be changing them.

The outgoing tree contains all the changes you intend for merge into
upstream. Publish this tree with {{{hg serve}}} or hgweb.cgi or use
{{{hg push}}}
to [:Push:push] it to another publicly available repository.

Then, for each feature you work on, create a new tree. [:Commit] early
and commit often, merge with incoming regularly, and once you're
satisfied with your feature, pull the changes into your outgoing tree.

=== Other 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 ||
|| ControlledPractice || good || medium || hierarchical development ||

=== See also ===
 * How to write good ChangeSetComments
 * RepositoryNaming is important, because you'll probably have lots of them
 * [:Clone]
 * MultipleCommitters

----
Question: Do you know which is the one HG takes itself?

 . Answer: Quote from [:ContributingChanges]: ''"Mercurial development process resembles the one described in KernelPractice"''

Question: What is the way to have ''commits'' go onto a backed-up drive? If my working computer is laptop with a safe `/samba` share?


----
CategoryHowTo
Hi. Let me start by introducing the author, his name is Monty. Baking is something his wife doesn't really wish but he does. Oregon is the only place he's been living in. Supervising is specifically he does for money but he plans relating to changing it. Check the latest news on his own website: http://apotopkredytowy.soup.io/

Hi. Let me start by introducing the author, his name is Monty. Baking is something his wife doesn't really wish but he does. Oregon is the only place he's been living in. Supervising is specifically he does for money but he plans relating to changing it. Check the latest news on his own website: http://apotopkredytowy.soup.io/

WorkingPractices (last edited 2013-08-31 09:38:15 by rcl)