Accessing configuration of remote repositories

Glenn Ammons ammons at us.ibm.com
Wed Nov 28 14:49:38 CST 2007


"Matt Mackall" <mpm at selenic.com> writes:

> On Wed, Nov 28, 2007 at 12:48:53AM -0500, Glenn Ammons wrote:

>> Is there a way to read an hgrc parameter for a remote repository?
>> If not, why not?
>
> No; there can be things like passwords there.

I suppose that could be handled with yet another configuration
parameter, which specifies which parameters can and can't be read by
other repositories, with a reasonable default.

>> I'd also appreciate suggestions about other places to keep this
>> information, so that it can be accessed remotely.
>
> You could check in a map.

I may be missing something, but I don't think that would work in my
case.  My parameter is really repository-specific, kind of like
"ui.username" is repository-specific.  If the map were versioned, then
a push from repository A to repository B would also push repository's
A parameter to B, even though A's parameter may be nonsense as a
parameter for B.

The only thing I've thought of, besides accessing the hgrc parameter
remotely, is to send the parameter out-of-band somehow.  For example,
the user could supply it on the command-line or an external database
could keep a map of Mercurial repositories to my hgrc parameter.  I
don't like this option.

Thanks.
--glenn


More information about the Mercurial-devel mailing list