log can't see historic filenames

Bug #175520 reported by Matthew Fuller
2
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Wishlist
Vincent Ladeuil

Bug Description

log won't let you limit by a file not in your current working tree.

bzr: ERROR: Path does not have any revision history: foo

#!/bin/sh -x
bzr="/usr/local/bin/bzr --no-aliases"

${bzr} init A
(
    cd A ;
    touch foo ;
    ${bzr} add ;
    ${bzr} ci -m '1' ;
    echo 'foo' > foo ;
    ${bzr} ci -m '2' ;
    rm foo ;
    ${bzr} ci -m '3' ;
    ${bzr} log -r..2 foo
)

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

Depending on the use case you may also track bug 136942

Changed in bzr:
importance: Undecided → Wishlist
status: New → Confirmed
Vincent Ladeuil (vila)
Changed in bzr:
assignee: nobody → vila
status: Confirmed → In Progress
status: In Progress → Fix Committed
Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

I think the core problem here is that "log -rX..Y foo" looks in the current/basis tree for foo. It ought to look in the revision tree of Y instead. After all, if I do something like "log -r..10 README", it ought to tell me about README in that historical context, whether or not it exists now.

The --status-flags option proposed in bug 136942 could help this use case: it will tell the user what revision a file was deleted in so they then know Y if they don't already.

Vincent Ladeuil (vila)
Changed in bzr:
milestone: none → 1.12rc1
status: Fix Committed → 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.