Cannot execute 'incoming' command to preview new changesets without writing to and reading from a local bundle file
Created originally on Bitbucket by colin-hurley (Colin Hurley)
The IncomingCommand writes a bundle file locally and reads from the bundle file. This creates unnecessary bandwidth usage if all you want to do is preview the incoming changesets without also transferring their commit data.
This also creates an issue for retrieving phase information for the changesets because reading the changesets from the bundle will (apparently) always make it appear that the changesets are in Draft phase, even if they are actually in Public phase in the remote repo. This bundle file behavior is what causes issue #512 in MercurialEclipse.
The IncomingCommand class needs to be revised so it does not force writing a bundle and so it returns a list of changesets (to match OutgoingCommand) instead of a bundle object.