Merge lp:~jbowtie/bzr/doc-bzr-st-historical-532600 into lp:bzr

[John C Barstow]

Make it clearer that 'bzr st' can be used to determine which files changed in a particular revision

Make it clearer that 'bzr st' can be used to determine which files have
changed in a particular revision.

[John A Meinel (jameinel)]

The way you rewrote it sounds like if you do "bzr status -r 10" that you will see the changes done in rev 10, but really it is the changes between the WT and revision 10. To see what happened *in* 10, you compare it to the previous with "bzr status -r 9..10" or possibly "bzr status -c 10".

review: Needs Fixing

[John C Barstow (jbowtie)]

I've updated the wording to make the distinction clearer.

[Vincent Ladeuil (vila)]

Works for me, thanks !

review: Approve

[Vincent Ladeuil (vila)]

sent to pqm by email

=== modified file 'bzrlib/builtins.py'
--- bzrlib/builtins.py	2010-09-15 10:40:51 +0000
+++ bzrlib/builtins.py	2010-09-20 01:01:06 +0000
@@ -250,8 +250,12 @@
     To skip the display of pending merge information altogether, use
     the no-pending option or specify a file/directory.
 
-    If a revision argument is given, the status is calculated against
-    that revision, or between two revisions if two are provided.
+    To compare the working directory to a specific revision, pass a
+    single revision to the revision argument.
+
+    To see which files have changed in a specific revision, or between
+    two revisions, pass a revision range to the revision argument.
+    This will produce the same results as calling 'bzr diff --summarize'.
     """
 
     # TODO: --no-recurse, --recurse options