Still no 'svn annotate' support?
|
|
Greetings, It’s very valuable to know when (and by whom) a given line was modified, especially when you’re dealing with a larger number of developers, all of whom are encouraged to actively fix/refactor things as they come across them. Even in one person projects, though, being able to click on a line of code and at least see the svn log message associated with the change that last affected that line would be a very helpful capability. Is this something you’re expecting plugin developers to do? It seems like some tight integration would be necessary to do it right. — Morgan |
|
|
We actually created the interface for it, but SVN doesn’t let you get annotation info from the actual repo. It only works from a working copy of the repo, which your server probably won’t have. It is possible that I may still add it, adding another task to the warehouse sync task. So, in addition to updating the database with the latest changeset info, it also updates the working copy that’s used for annotations. |
|
|
Greetings, The command:
works pretty well, and there’s a—xml parameter which could help extract the info you’d need. (Note the space after http:, because I can’t figure out how to make it not auto link the URL, and just leave it in text form.) It’d be better if you can rely on subversion, but you may (understandably) not want to fix the Ruby/Subversion bindings. — Morgan |
|
|
Greetings, Is that not what you mean? For local repositories, I think you can also put — Morgan |
|
|
Oh really? Hmm, I’ll have to give that another shot. I’d personally love to get this in there. Thanks for the help. |
|
|
So, not only does this work, it seems to be fast too (since it’s being called from the actual repo and not a working copy). We’re just figuring out how to do all this efficiently, provide fallbacks for those not using Ultraviolet. We should have a release out very soon. |