preliminary guide to Mercurial via workflows

[David I.]

> > I think if you have a centralized workflow example where all changes

> > are eventually pushed to the central repository, that is good enough

> > for a corporate developer to understand. One level is to show how
the 
> > central repository is on a shared filesystem, another layer is to
show 
> > it on a remote server accessed over SSH.

> Maybe we can add these as a note. 
>
> --- --- --- --- --- ---
> Note: You can also use this workflow with a shared server instead of
BitBucket, either via SSH or via a 
> shared directory. An example for an SSH URL with Mercurial is be
ssh://hg@bitbucket.org/ArneBab/1w6 (for a 
> shared server you'd replace the "hg" in the given URL with your
username). For a shared directory you just 
> push as if the repository in the shared directory were on your local
drive. 
> --- --- --- --- --- --- 

That note sounds good to me, but I also agree with Kevin's comment on
using a different example username.  


David  


-----Original Message-----
From: arne_bab at web.de [mailto:arne_bab at web.de] On Behalf Of Arne
Babenhauserheide arne_bab-at-web.de |Mercurial|
Sent: Monday, May 11, 2009 9:21 AM
To: Ishee, David M
Cc: David I.
Subject: Re: preliminary guide to Mercurial via workflows