Accessing configuration of remote repositories

Matt Mackall mpm at selenic.com
Wed Nov 28 15:20:20 CST 2007


On Wed, Nov 28, 2007 at 03:49:38PM -0500, Glenn Ammons wrote:
> "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.

Well there's also no provision for it in the wire protocol (which is
very simple).
 
> >> 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.

Imagine everyone writes a single line each to upstream.txt of the form:

repo-url upstream-repo-url

> 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.

-- 
Mathematics is the supreme nostalgia of our time.


More information about the Mercurial-devel mailing list