what do I need to learn to do this task?
Justinas Urbanavicius
justinasu at gmail.com
Tue May 13 06:28:24 UTC 2014
well i agree about the advantages of using SCM instead of synchronizing.
One last though, why don't you use a thumb drive, clone the source files in
it, plug it in on desktop, do your work, then plug it in on notebook,
continue your work, do commits as you please when you think it's right :)
No network, no pushing or pulling, and you can push or pull from either
computer to and from your bitbucket cloud :)
On Tue, May 13, 2014 at 9:15 AM, Michael Mossey <michaelmossey at gmail.com>wrote:
> On 5/12/2014 11:08 PM, Justinas Urbanavicius wrote:
>
>> well each of repository is already a backup by itself, 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
>>
>>
> I agree with what you are saying, but I just think it's even better to
> have a cloud backup, and also the essence of my problem is that I need to
> do a lot of meaningless commits that represent nothing more than when I had
> to switch computers.
>
> You might ask, is a SCM the right tool for synchronizing work between two
> computers? It certainly has a lot of advantages. If I forget which computer
> I worked on last, or somehow make changes on both computers, the SCM will
> give me the whole status and do merges if necessary.
>
>
> Mike
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
--
Justinas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140513/e5f9a308/attachment-0002.html>
More information about the Mercurial
mailing list