what do I need to learn to do this task?

Dave S snidely.too at gmail.com
Tue May 13 06:18:55 UTC 2014


On May 12, 2014 11:08 PM, "Justinas Urbanavicius" <justinasu at gmail.com>
wrote:
>
> well each of repository is already a backup by itself,

That's true from a changeset perspective, but not from a crash perspective.

> and i don't think you have to learn anything special. hg serve command
shows you what ip/host your server is running on so you just need to write
it into your config.
>
> either way i think you are using mercurial as a backup tool more than a
version control, some people like to do commits, paranoiacally as often as
using save in word :)
> but i don't think it's a good practice, each commit should be meaningful,
a change that reflects something

And I vote for the middle ground.  Don't wait for "release-ready"; do
commit at least as often as natural breaks occur.  From the point of view
of being able to unwind mistakes, more ci beats less ci.

/dps
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140512/d097bfea/attachment-0002.html>


More information about the Mercurial mailing list