bzr st docs are not clear about using historical revisions
Bug #532600 reported by
Per Johansson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
svn diff has a useful --summarize flag to show what files changed between two revision. It is similar to the extra info output by log -v, but you can apply it to any two revisions. Eg:
$ bzr diff --summarize -r -3..
modified:
__init__.py
log.py
bzr can do this using 'bzr status' but this could be documented or made more clear in the help (of diff, status, or the user guide.)
Related branches
lp:~jbowtie/bzr/doc-bzr-st-historical-532600
- Vincent Ladeuil: Approve
- John A Meinel: Needs Fixing
-
Diff: 18 lines (+6/-2)1 file modifiedbzrlib/builtins.py (+6/-2)
description: | updated |
Changed in bzr: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Low |
tags: | added: diff doc easy help status |
summary: |
- bzr diff --summarize + bzr st docs are not clear about using historical evisions |
Changed in bzr: | |
importance: | Low → Wishlist |
tags: | removed: diff easy help status |
summary: |
- bzr st docs are not clear about using historical evisions + bzr st docs are not clear about using historical revisions |
tags: | added: check-for-breezy |
To post a comment you must log in.
The bzr-diffstat plugin (http:// launchpad. net/bzr- diffstat) provides a similar summary, using a format similar to git's diff stat. After installation, it is available as ``bzr diff --stat``.