[Python-Dev] Submitting changes through Mercurial

[Carl Meyer]

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

Hi Senthil,

On 03/21/2011 09:57 PM, Senthil Kumaran wrote:
> - In the above issue, why is two same bitbutket urls are provided. (It
> is redundant).

I updated the patch, and the second time around the "remote hg repo" box
was empty. I wasn't sure what to do so I filled it again. Probably would
be nice if this was detected and the repo not listed a second time.

> - Also, how is it that system is creating patch from a repository
> outside of hg.python.org? What if the user had an older version in
> remote repo and tip in the hg.python.org has moved forward?

Don't know exactly how it's implemented, but I would guess it's using
"hg incoming --patch" or similar, which would handle this transparently;
the newer revisions at hg.python.org would just be ignored in generating
the diff.

Carl


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

iEYEARECAAYFAk2IBiQACgkQFRcxmeyPUXLnTACeII/z+gSZPt5d1ycyn2rcqaxr
4/kAn3l/JQdT2lMk2M6Ll+EA4mTEo39B
=hxIJ
-----END PGP SIGNATURE-----