[Python-Dev] hg diff
Adrian Buehlmann
adrian at cadifra.com
Tue Mar 8 11:07:55 CET 2011
On 2011-03-08 10:53, Adrian Buehlmann wrote:
> On 2011-03-08 09:38, "Martin v. Löwis" wrote:
>>> However, as Michael points out, you can have your tools generate the
>>> patch. For example, it shouldn't be too hard to add a dynamic patch
>>> generator to Roundup (although I haven't thought about the UI or the
>>> CPU burden).
>>
>> For Mercurial, that's more difficult than you might expect. There is "hg
>> incoming -p", but it has the nasty problem that it may produce
>> multiple patches for a single file.
>
> I didn't follow/understand closely/completely what your problems is, but
> I wouldn't be surprised if mercurial's 'incoming' command has its
> limitations (it's most likely intentional, since remote inspection is
> limited on purpose and frowned upon by design).
>
> In general, you have to have all the changesets in a local repo to enjoy
> the full power of mercurial's history inspection tools.
>
> Maybe the following trick could be interesting for you:
>
> If you don't want to do an outright pull from a (possibly dubious)
> remote repo into your precious local repo yet, you can instead
> "superimpose" a separate overlay bundle file on your local repo.
OOPS. I failed to notice that this has already been proposed in the
thread "combined hg incoming patch".
Sorry for the noise.
More information about the Python-Dev
mailing list