store/retrieve push and pull locations

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 3/8/2011 1:01 PM, Jelmer Vernooij wrote:
> Public bug reported:
>
> these locations should be retrieved from the .hgrc file, preferably from
> a setting mercurial also uses
>
> ** Affects: bzr-hg
> Importance: Medium
> Status: Triaged
>
>
> ** Tags: completeness
>

Note that from what I've read, mercurial's main dev explicitly doesn't
like writing to hgrc. He wants users to edit it themselves. So I'm
guessing mercurial won't have an api to write to the config file.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk12IRIACgkQJdeBCYSNAAOnaQCgkeh1jQu0sS1YLUp4vX3SqWwn
mvkAoJZbYwGiuXYVGqyrY66uRxpKa6yV
=OOME
-----END PGP SIGNATURE-----

On Tue, 2011-03-08 at 12:29 +0000, John A Meinel wrote:
> On 3/8/2011 1:01 PM, Jelmer Vernooij wrote:
> > Public bug reported:
> >
> > these locations should be retrieved from the .hgrc file, preferably from
> > a setting mercurial also uses
> >
> > ** Affects: bzr-hg
> > Importance: Medium
> > Status: Triaged
> >
> >
> > ** Tags: completeness
> >
>
> Note that from what I've read, mercurial's main dev explicitly doesn't
> like writing to hgrc. He wants users to edit it themselves. So I'm
> guessing mercurial won't have an api to write to the config file.
There is an API which, I have to say, is easier to use than the current
bzr config API... :)

bzr-hg already wraps this API to e.g. set custom user options.

Cheers,

Jelmer