comparison mercurial/discovery.py @ 15893:eb6867b98223

discovery: fix prepush documentation

The prepush documentation claim that when we refuse to push, the second element
of the returng tuple is an "outgoing" integer. value should be 0 when no
outgoing changeset and 1 otherwise.  In pratice if there are no outgoing
changeset, "outgoing" value is alway 1 and util.Abort is raised on other error.

the stable branch also include this error so it wasn't introduced by a recent
refactoring.

15892:592b3d1742a1

def prepush(repo, remote, force, revs, newbranch):
    '''Analyze the local and remote repositories and determine which
    changesets need to be pushed to the remote. Return value depends
    on circumstances:

    If we are not going to push anything, return a tuple (None,
    outgoing, common) where outgoing is 0 if there are no outgoing
    changesets and 1 if there are, but we refuse to push them
    (e.g. would create new remote heads). The third element "common"
    is the list of heads of the common set between local and remote.

    Otherwise, return a tuple (changegroup, remoteheads, futureheads),
    where changegroup is a readable file-like object whose read()
    returns successive changegroup chunks ready to be sent over the
    wire, remoteheads is the list of remote heads and futureheads is

15893:eb6867b98223

def prepush(repo, remote, force, revs, newbranch):
    '''Analyze the local and remote repositories and determine which
    changesets need to be pushed to the remote. Return value depends
    on circumstances:

    If we are not going to push anything, return a tuple (None, 1,
    common) The third element "common" is the list of heads of the
    common set between local and remote.

    Otherwise, return a tuple (changegroup, remoteheads, futureheads),
    where changegroup is a readable file-like object whose read()
    returns successive changegroup chunks ready to be sent over the
    wire, remoteheads is the list of remote heads and futureheads is