[MERGE] Better/faster status after merge

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian Clatworthy wrote:
> In response to Vincent's RFC about how various commands
> display revisions, I wrote on 25/09/2008:
> 
>> The main command *I* care about the most is status and I'd like
>> us to consider changing how we display non-mainline revisions there.
>>
>> By default, I'd like status to show just the *merge tips* if there
>> are any. I'd like status -v to show the full list of merge revisions.
>> In particular, when merging from trunk into a feature branch right
>> now, 'bzr status' can show 100s of revisions and they are just
>> noise. I find myself constantly using --no-pending in this case to
>> see the list of files that has since scrolled off the screen.  :-( 
>> Showing just the tips will also be *much* quicker.
> 
> Martin Pool's response (also 25/09/2008) was:
> 
>> +1, both on simplicity and speed.
> 
> Here's a patch implementing this change.
> 
> Ian C.
> 

Seems like a good patch. This is also something I would want early on in
a dev cycle so that we can decide if people really like the UI changes.

I wonder if we might want to do something like:

pending merge tips: (use --verbose to see all merged revisions)
  John Arbash Meinel xxyyyzzz

I think we have the screen real-estate for it, and it helps point people
to get the data that they used to get.

The statement is a bit verbose itself, so we may want to reword it, but
I thought it might be helpful.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklso4IACgkQJdeBCYSNAAPvMACdGD3kaMvVQ1sG6SpdNtf//GzG
zmwAmwdnwvsA4jbqcM5brWsBxjJZLkrA
=iRVI
-----END PGP SIGNATURE-----