While working on a project, I realized I wanted to add some code that parts of it existed in a file I deleted along with other deprecated old files. It would shorten my work to copy/paste (or at least view) some of the code I had in that old file.
$ svn log -v
This command showed me very nicely a lot of commit messages, but.. something is off.
I try this instead:
$ svn log -v | perl -nle'/\s+D\w/ && print'
Nothing. Since I don't know when I have finished committing changes to it, I don't know which revision of it I should get. I'm beginning to dislike subversion...
In Git, by the way:
$ git --no-pager log --name-status | perl -nle'/^D\s+/ && print'
You may say "this is pretty long" or "see? that's complex" but:
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: (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".
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
try specifying the URL (Score:1)
Re: (Score:1)
I did.
But thank you anyway.
Pay attention to your cwd (Score:1)
I'm guessing git is like mercurial, in that it shows you the commit log for the entire repo no matter what your cwd. Subversion, on the other hand, only shows you the commit log for any paths at your cwd or deeper. If you cd into the root of your repo's trunk, svn log may list more of your commits.
--no-pager not needed (Score:1)