On 11/16/06, Nikki Locke <firstname.lastname@example.org> wrote:
> Wouldn't the release be tagged in SVN (perhaps as
> Then you scan the history of that file in /tags/production/20061115a, and
> see if the fix is in there [DON'T set the "stop on copy" flag].
Yes you're right, and that's what I do. My current approach to that is to
fire up the ToroiseSVN repo-browser, browse to the file, and do as you say.
> What's the difference?
Convenience. The may simply be a limitation in IntelliJ IDEA, but when we
used CVS I could do this operation in two clicks. The above means changing
to another program, finding the file and _then_ looking for history.
Thinking further about this there's no reason I couldn't do this in IntelliJ
but I would still have the additional step of browsing to the copy of the
file in question before looking for where it was copied from.
I think the real difference is that in CVS a tag is _on_ a file, so I'm
simply saying "show me the history and I'll scan it myself to see which
version a tag is on". In SVN a tag is simply a copy, and because (afaik)
SVN has no support to seeing where a particular file has been copied _to_ it
is not possible to do the same in SVN - instead I have to look at the copy
(which I don't have at hand) and see where it was copied _from_.
Received on Wed Nov 15 20:57:52 2006