On 7/31/13 5:59 PM, Justin Lebar wrote:
Sadly, mercurial doesn't support having multiple working directories
from a single clone, which would be useful to avoid wasting so much disk
space on .hg.
I'm not usually one to defend hg, but hg does have the |relink|
command, which gets you most of the way there in terms of saving disk
space.
There's also the share extension [1]. Although, it doesn't play well
with mq and other history editing commands. Works great for automated
environments, however.
[1] http://mercurial.selenic.com/wiki/ShareExtension
On Wed, Jul 31, 2013 at 5:57 PM, Mike Hommey <m...@glandium.org> wrote:
On Wed, Jul 31, 2013 at 10:28:38AM -0700, Justin Lebar wrote:
Wouldn't switching branches in the same repo clone touch many files
and trigger unfortunately clobber builds? Even with ccache and
separate per-branch objdirs, this seems like a problem.
Yes.
Nothing about this proposal forces you to have only one clone and
switch back and forth between aurora and central, thus clobbering your
objdir. You could still have two trees, one used for aurora, and one
used for central, if you prefer that.
Sadly, mercurial doesn't support having multiple working directories
from a single clone, which would be useful to avoid wasting so much disk
space on .hg. But git does ;) (albeit, with a script in contrib/)
I guess someone could patch mercurial to support such setups, which,
independently of what we do on the servers, could be useful on the
clients (pull different branches in the same local clone, use different
working directories for each).
Mike
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
