Detecting conflicts that a pull would cause wothout actually pulling

[till plewe]

On Fri, Jun 17, 2011 at 11:58 PM, Akos Tajti <akos.tajti at gmail.com> wrote:

> Dear List,
>
> I'd like to solve the following problem:
> I have a repository (call it A) and a clone of it (call it B). I made some
> changes in B and I want to ask the owner of A to pull it. I'd like to
> implement a function that can figure out if the changes in B can be pulled
> to A without causing any conflicts. I want to implement this in such a way
> that doesn't corrupt the information in A (so anyone who clones A sees
> exactly the same than before this confict detection).
>
>
Is "hg incoming" or if you want to avoid multiple downloads "hg incoming
--bundle" insufficient?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20110618/8af78529/attachment.htm>