NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
svn log is alright (Score:1)
Sorry, but svn log -v works. You're either not looking at the code or you didn't commit a delete on the file.
Re:svn log is alright (Score:1)
Even though Shlomi Fish grilled me for about half an hour on what I did and how I did it to find the missing file, I will show it here as well anyway, because "Seeing is believing".
As you can see,
svn statusshows that I have one changed file (Changes) and one untracked file (output_log.txt), so I have no uncommitted deletions or additions.When I search
svn logfor a file called 10-eg_server.t, I can only see that it was added, along with the actual path.However, when I ask for the log of a specific revision (r13831), I can see the deletion of the file 10-eg_server.t, along with another file. The problem here is that
svn log -vwill return only certain things without any persistency (it will show changes as well as additions and deletions but this time it only showed the addition of the file, not deletion), and return other things when asking for the log of a specific revision.So, subversion is stupid.
But thank you for automatically assuming Subversion is impeccable, and I was wrong.
Reply to This
Parent
Re: (Score:1)
I wasn't trying to be insulting. It's only reasonable to look for user mistakes or misunderstanding before assuming that a behavior in a widely used piece of software is a bug. Think of how many times people have reported they found a bug in Perl and how many times they actually had.
I suspect there's an answer for this one involving either how the paths under CWD are figured or which revisions are shown when no number is specified. If you actually want to solve it, I suspect you'd be better off asking on