Visual-studio – Does tortoise or ankh svn have log dump capability

changelogsvnvisual studio

I'd like to include revision history in a menu system of my builds so that users can see it and it's auto-built from the svn repository before each build. My team doesn't have the core svn, only tortoise and ankh. I'd rather not have to go through configuration of it on each machine we use just for this feature if one of the tools we already have can do it.

I'm looking for something that does ANY full revision log dump like

svn log
svn log –xml
svn log -v

but built into ankh or tortoise.

i've been searching their documentation and websites with no luck so far, any ideas?

Best Answer

TortoiseSVN doesn’t have the ability to do this, and I doubt Ankh does either. The command line is the way to do it. If you don’t want to install a command-line client on every machine, you could consolidate your build process so that there is a dedicated build machine which does it.

Related Solutions

Git – How to have ‘git log’ show filenames like ‘svn log -v’

For full path names of changed files:

git log --name-only

For full path names and status of changed files:

git log --name-status

For abbreviated pathnames and a diffstat of changed files:

git log --stat

There are a lot more options. Check out the documentation.

Reintegrate can only be used if revisions X through Y were previously merged from to reintegrate the source, but this is not the case

If you are working on a branch and have been keeping it up to date with others work you might be bemused when you create a working copy of the trunk and attempt to reintegrate your branch if you get a message something like this:

$ svn merge --reintegrate https://server.blah/source/orb/branches/bronze_services
svn: Reintegrate can only be used if revisions 650 through 694 were previously merged from
     https://server.blah/source/orb/trunk to the reintegrate source, but this is not the
     case:
  branches/bronze_services/occl
    Missing ranges: /trunk/occl:650-693

I've seen a number of workarounds on Google but they made me nervous as 'hacks'. To address it I decided to do just what subversion is hinting at in the message. I went back to my branch and explicitly merged the specified revisions:

$ svn merge -r 650:693 https://server.blah/source/orb/trunk
$ svn commit -m 'merged revisions 650:693 from trunk'
    Sending        occl
Committed revision 695.

Once I did this, I was able to return to the working copy of trunk and reintegrate the branch without any problems.

I hope this helps

Best Answer

Related Solutions

Git – How to have ‘git log’ show filenames like ‘svn log -v’

Reintegrate can only be used if revisions X through Y were previously merged from to reintegrate the source, but this is not the case

Related Topic