what do I need to learn to do this task?

[Michael Mossey]

On Mon, May 12, 2014 at 7:08 PM, Adrian Klaver <adrian.klaver at aklaver.com>wrote:

> On 05/12/2014 06:17 PM, Michael Mossey wrote:
>
>> I'm new to Mercurial and I don't have a lot of time to devote to
>> learning it (or any SCM system) in great detail, nor do I need to, so I
>> am wondering if I could get some guidance about the specific things I
>> need to do this task:
>>
>> My workflow will look something like this:
>>
>> (1) I'll check out a copy of the main Bitbucket repo
>> (2) I'll work on my laptop
>> (3) I'll be ready to switch to my desktop, so I'll commit changes
>> (3) I'll push changes to some kind of secondary Bitbucket repo
>> (4) I'll get on my desktop and pull those changes, and work
>> (5) Get ready to switch to laptop; commit changes and push to secondary
>> BB repo again
>> (6) Continue, creating possibly a dozen small meaningless changesets
>> until ready to commit a feature or intermediate feature to main BB repo
>> (7) here's the trick I don't understand--somehow push and/or merge my
>> changes with the main BB repo, hopefully without pushing a bunch of
>> meaningless changesets onto it
>>
>> So basically I'm wondering how to structure things so I can do (7)
>>
>
> Well I avoid the whole issue by using Unison (http://www.cis.upenn.edu/~
> bcpierce/unison/) for the middle part. Basically you want the
> laptop/desktop to be the same machine and then push/pull from Bitbucket. I
> just do work on either my laptop or desktop and the use Unison to sync with
> an EC2 instance. I then sync from that to the other machine. So:
>
>    ->   EC2 < -
>    |            |
>   \/           \/
> laptop          desktop
>
> This way I do not have to commit until I want to and then push/pull to
> Bitbucket.
>


I don't think this is going to work for me as I have no access to a server
to run Unison.

And, I still want to use Mercurial to do this because I think it's a good
use case for familiarizing myself with Mercurial basics.

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