bzr log should accept multiple files

Bug #211852 reported by Stefan Monnier
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

Currently "bzr log" only accepts a single "location", but it would make a lot of sense to allow multiple files to be specified. It is already possible to specify more than one file but less than the whole tree, by specifying a subdirectory, so there doesn't seem to be any good reason to disallow specifying a list of files (or subdirectories), just as it is accepted by "bzr diff", "bzr revert", ...

It seems this is linked to the fact that a branch can be specified instead of a file, but maybe the two should not be conflated since I may very well want to see the log for file <foo> in branch sftp://host/bar.

Revision history for this message
Vincent Ladeuil (vila) wrote :

Indeed bzr log accepts a single argument which is dwimified into either a branch path or a file/dir path.

I think the rationale was that they are the most common use cases. This need to be revisited to handle your use cases.

Changed in bzr:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
dann (dann-ics) wrote :

1. bzr log SUBDIR
does not seem to DTRT, it only lists a single log entry, it should show the logs for all the changes in that subdirectory.
When working on a big project, one might just want to look at what changed in a particular subdirectory, this is where such a command comes in handy.

is also extremely useful, sometimes when hunting a bug, you can suspect that it can be in FILE1.c FILE1.h or FILE2.c
then doing a bzr log for those files is a very easy way to find the last changes for them.

Karl Fogel (kfogel)
description: updated
Revision history for this message
Karl Fogel (kfogel) wrote :

Case 2 in dann's comment above is a separate issue, and is filed:

Revision history for this message
Karl Fogel (kfogel) wrote :
Revision history for this message
Karl Fogel (kfogel) wrote :

And this other thread, while not directly relevant to fixing the bug, explains why some developers want the fix:

Revision history for this message
Marius Kruger (amanica) wrote :

The fix for this snuck into 1.13.2 where you can now do for example:
(selected the earliest milestone)

Changed in bzr:
milestone: none → 1.14rc2
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.