[Bug 3577] New: pre-push hook determines changesets to send before running pre-push hook

[bugzilla-daemon at bz.selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3577

          Priority: normal
            Bug ID: 3577
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: pre-push hook determines changesets to send before
                    running pre-push hook
          Severity: bug
    Classification: Unclassified
                OS: All
          Reporter: thombend at selinc.com
          Hardware: All
            Status: UNCONFIRMED
           Version: 2.2.3
         Component: Mercurial
           Product: Mercurial

The documentation for this hook suggests that the hook will be run before
executing the "associated command."

Unfortunately, if a changeset is generated by the pre-push command, any
generated/copied/pulled changesets produced by the hook will not be pushed.

There is already a hook which does this, it seems: prechangegroup.

I would propose that expected behavior is that the pre-push hook would be run
before the push command began identifying outgoing changesets.

-- 
You are receiving this mail because:
You are on the CC list for the bug.