Lame question about where to make the first repository

Greg Ward greg-hg at gerg.ca
Fri Apr 9 11:12:55 CDT 2010


On Fri, Apr 9, 2010 at 7:43 AM, qwerty360 <qwerty360 at gmail.com> wrote:
> On Thu, Apr 8, 2010 at 6:19 PM, Ken Egervari <ken.egervari at gmail.com> wrote:
>> The main reason I wanted to use something like mercurial is that I often
>> find myself having to work on a few features at a time. Sometimes 8 out of
>> the 10 features are small additions while 2 out of the 10 are multi-day
>> marathons ;) What I'd like to do is work on the marthon feature in 1 project
>> and still be able to add those smaller features to a totally different
>> branch.
>
> For this you should look at the mercurial queues extension (mq).

No, he should *not* look at mq (yet).  Please don't refer beginners to
advanced extensions like mq.  You can get quite a lot of useful work
done without ever using mq, and it can be very confusing when you're
first using it.  If you try to learn mq at the same time as you're
still learning hg, you're almost guaranteed to have a hard time of it.

Ken: the usual approach to what you want to do is to have multiple
local clones.  E.g. have one clone for quick bug fixes and one clone
for each "marathon" change.  That lets you get the bug fixes out
quickly, and then you can merge in the big changes when they are
ready.

There are of course other ways to do it, but that's the simplest and
most straightforward.

Greg


More information about the Mercurial mailing list