[PATCH] Support remote access to (some) "hgrc" parameters

[Matt Mackall]

On Thu, 2008-01-03 at 04:29 -0500, Glenn Ammons wrote:
> "Peter Arrenbrecht" <peter.arrenbrecht at gmail.com> writes:
> 
> > What is the point? Can [public.foo] already be used interchangeably
> > with [foo] for the purpose of configuring things, or will public.*
> > have to be queried separately by future configurable elements? What am
> > I missing here?
> > -peter
> 
> Sorry, I should have given more context in the patch.
> 
> I'm writing an extension of "hg pull" and "hg push"; the extension
> needs to query the configuration of the source/target repository but
> there's currently no way for an extension to do that.  I asked about
> remote access a few weeks ago, to an unenthusiastic reception, but
> thought that an implementation would be something concrete to talk
> about, particularly since one of the objections was about
> over-complicating the protocols.  The previous thread starts here:
> 
>     http://www.selenic.com/pipermail/mercurial-devel/2007-November/003559.html
> 

Can this protocol extension to hgweb also go in an extension?

-- 
Mathematics is the supreme nostalgia of our time.