On 12/22/05, Magee, Glen <firstname.lastname@example.org> wrote:
> I have encountered an unexpected behavior when using "Show log" from a wc
> (it works fine from the repository browser). As I understand it, "Show log"
> uses the HEAD revision as the default when requesting information from the
> repository. So when I check out an older revision of the repository and try
> to check the log for a file that does not exist in the HEAD, I receive a
> "File not found" message. Perhaps the default revisions for non-HEAD
> check-outs could be the requested revision? That may cause other problems I
> have not considered, though.
> To reproduce:
> 1) Check out a repository.
> 2) Add a new file, "test_file.txt".
> 3) Commit. Record the repository revision number.
> 4) Delete "test_file.txt".
> 5) Commit.
> 6) Check out the pre-delete revision of the repository (i.e., the revision
> noted in step 3).
> 7) Right-click on "test_file.txt" and select TortoiseSVN->Show log.
> Expected Behavior:
> The pre-deletion log for the deleted file.
> Actual Behavior:
> "File not found".
> The dialogue box doesn't even allow the selection of another revision like
> the "Show log" dialogue from the repository browser does.
> I can work around this behavior, but I thought I'd report it anyway. Thanks
> for your time,
As you noticed, "show log" always uses the HEAD revision, or the
revision from the repository browser it was started with. So it would
be *really* bad if (as you'd like it to) it just would show you the
log from the checked out revision. How would you then know from the
log that the folder isn't even there anymore?
For example, the CL client uses BASE as the peg revision when showing
a log. But this is *very* confusing for users, because if they show
the log, they never see commits from others since their last update.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Dec 25 02:27:14 2005