P4D3::Mercurial::Output from outgoing with exclude merges feels incomplete

Create issue
Issue #72 resolved
timeless developer created an issue

== Steps ==

Use the files from issue <<issue 61>>

Select repository "test"

Click Clone

short name "current"

localpath "/private/tmp/test-hgClone2"

Click Clone repository

Click outgoing

Select 'current'

Open advanced options and ensure 'Exclude merges' is unchecked

Click OK

Click outgoing

Select 'testClone'

Open advanced options and ensure 'Exclude merges' is checked

Click OK

== Expected Results == {{{ comparing with /private/tmp/test-hgClone2 searching for changes no changes found }}}

{{{ comparing with /private/tmp/test-hgClone searching for changes no [excluded] changes found }}}

== Actual Results == {{{ comparing with /private/tmp/test-hgClone2 searching for changes no changes found }}}

{{{ comparing with /private/tmp/test-hgClone searching for changes }}}

Comments (2)

  1. Jason Harris repo owner

    Weeellll... Unfortunately, I am just giving the results back that straight Mercurial gives. This would be the same results you see on the command line. I agree that you are right here, but this is a Mercurial issue.

    I guess you could report it as a bug to the Mercurial crowd. But unfortunately I asked for something much higher priority than this which was for improved error code support so that all GUI's can operate better, and Matt Mackall was quite hostile and abrasive over this. (You can read the sordid email logs on the Mercurial mailing list...) Thus having a consistent message here is I guess fairly low on their priorities. Or maybe he will turn around and yell at you to fix it yourself, as he did to me... Then again maybe it will meet with a sympathetic ear from one of the friendly developers. I just don't know. If you do report it good luck :) But I'll close this as not a MacHg issue but a Mercurial issue...

    Thanks for the report though!

  2. Log in to comment