Greetings, Les Mikesell! >>>> Binary search on the 0 to HEAD revision range is a possibility, but it's >>>> also a rather wasteful workaround. >> >>> Fisheye (a commercial product) does a brute-force extract/index of all >>> the filenames and content in all revs in a repo for quick searches. >>> I'm not sure if there is any equivalent open source program but this is >>> probably the right answer for anyone who needs to do that frequently. >> >> Sorry, do you mean that we have to pay to cover the lack of functionality in >> Subversion? And it should remain this way?
> Yes, I would not expect fast indexed full-text searches across names and > content > to ever be a part of the version control system itself. But the > functionality > to find filename changes is there - just 'log -v' from the top. Where you see a reference to full-text search in my quote? I have intentionally omit that part of your reply. >>> There's a big problem here - whether a URL exists or not usually isn't >>> the right answer for things that have been deleted and replaced by >>> something else of the same name. >> >> I strongly suspect that Ludwig had in mind that Subversion could track >> revisions in which file has been changed in either way. >> Then no way you could confuse between different files with same URL. > It does track that, but I don't think there is a convenient way to ask for > it. > Or for the server itself to find it efficiently. It only track it back into the past. There's no sane way to track it forward currently. I see some complications in implementation of this ability, mainly in the controversial way it should work (i.e. alter multiple previous revisions to embed the forward tracking links, or to maintain a parallel base for them). -- WBR, Andrey Repin (anrdae...@freemail.ru) 30.11.2010, <21:10> Sorry for my terrible english...
