"bzr log --line --verbose" does not work
Bug #140844 reported by
stevage
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
This may sound counterintuitive but it would be useful. Bzr log --line gives this format:
6: DMB 1990-03-14 Add PAGEn; set_autopage use pdesc
5: DMB 1990-03-08 Fix INDEX_SET batch bug
Bzr log --line --verbose could give something like this:
6: DMB 1990-03-14 [GENFILE.C] Add PAGEn; set_autopage use pdesc
5: DMB 1990-03-08 [REINDEX.C] Fix INDEX_SET batch bug
It would also be good if there was a way of showing nested commits in this line format. I'm not sure what the real term is, but when you have some --local commits that are then committed on a higher level. "Bzr log" has a very nice nested display, so a line-based version would be great, too.
Revision history for this message
| Vincent Begaut (dr-virago) wrote | #1 |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #2 |
| Changed in bzr: | |
| status: | New → Fix Released |
To post a comment you must log in.
Following my question #23404 (https:/
Motivation is that 'bzr log' is currently the only reliable interface to retrieve the reference revision for a file that was removed.
Coupling '--line' with '--verbose' would ease that lookup, without altering the purpose of '--line' filter.
As side note (maybe it would deserve its own bug report):
I do not know how it operates internally but I noticed the following discrepancies:
- 'bzr log --line' is as fast as 'bzr log --line --verbose', as if 'verbose' option was discarded due to filter '--line'
- however, 'bzr missing --line --verbose' still does not display file updates, but is much slower than 'bzr missing --line' alone.
(all of this using bzr 1.1)