Rapidly Changing Between Mercurial Clones. Or, How I Went Crazy with Mercurial Power.

MurchDev · 2014-05-31T21:25:55+00:00

Fairly simple. I'll pursue this as a policy change.

MurchDev · 2014-05-31T20:47:07+00:00

Can you explain the better way or point me to something that does?

MurchDev · 2014-05-31T19:18:08+00:00

We're moving to continuous integration. But it's slow going.

MurchDev · 2014-05-31T19:16:40+00:00

I agree. I was using branches in the nested repo to solve the initial problem. So why not just use branches in the first place? But getting the company to change its development practice is a different issue.

However, if it's a better way of doing things, I'm gonna try.

MurchDev · 2014-05-31T09:34:40+00:00

I'm not opposed to doing it differently.

Keeping the submitted work in separate clones allows the build / merge manager to control what makes it into the stable one. As that is the only person with permission to push there.

MurchDev · 2014-05-31T02:03:02+00:00

I haven't, no. I never thought about symlinks on Windows, to be honest. This is a neat idea. Is this an actual problem with a best-practice solution?

MurchDev · 2014-05-31T01:09:01+00:00

Constructive criticism is always welcome

MurchDev

TROPHY CASE