Lame question about where to make the first repository

[Ken Egervari]

Hi Greg,

Yeah, that's how I plan on doing it. That clone feature is so amazing. I was
playing with it yesterday for fun. Mercurial is the best thing to come out
in a long time. I am so jealous of everyone who has been using it for as
long as they have. I've totally missed out.

SVN is so terrible. Mercurial is everything I wanted and more. That HgInit
site was a big help to teaching me the basics and I've just been running
with it all yesterday.  Gotta say, I'm loving it.

There's even a plugin for IntelliJ IDEA, so that definitely makes
adding/removing/moving files easier, although sometimes I like to use the
command line just so I know what's going on.

Very happy ;)

Ken


On Fri, Apr 9, 2010 at 12:12 PM, Greg Ward <greg-hg at gerg.ca> wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20100409/24a0bc75/attachment.htm>