preliminary guide to Mercurial via workflows

[Arne Babenhauserheide]

On Tuesday, 5. May 2009 15:47:52 David I. wrote:
> 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. 

How about this one: 

--- --- --- --- --- --- 
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. 
--- --- --- --- --- --- 

Best wishes, 
Arne

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -
              http://infinite-hands.draketo.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20090511/015fb9fe/attachment.pgp