[PATCH] Check for .hgrc files in ancestor directories above the repository

Peter Arrenbrecht peter.arrenbrecht at gmail.com
Sat Jan 12 01:46:59 CST 2008


On Jan 11, 2008 10:22 PM, Jesse Glick <jesse.glick at sun.com> wrote:
> John Coomes wrote:
> > Here's a modified proposal: If .hg/hgrc has a [clonable] section,
> > then the items listed there should be copied when the repo is cloned,
> > subject to the usual user restrictions. Items in the [clonable]
> > section are just names without values.
>
> I would be happy with this too. Simpler to explain than any of the
> include-file proposals, handles the basic use case. Anyone else?

I still like includes better (see my latest re-explained proposal with
.hginclude files).

I normally have a dedicated parent folder for all of my clones of a
particular project (for example hg, hg-stable, crew, ... all within a
parent "hg" folder). Now when I clone another remote repo
(crew-stable, or some contributor's, for instance), the include file
approach would work immediately. The copy-on-clone approach would not.

Sometimes I also start the remote clones from scratch again (my way of
reestablishing hardlinks - maybe not the best way). Same problem then.

So while I could live with copy-on-clone, I would prefer includes.

-peo


More information about the Mercurial-devel mailing list