On Sun, Mar 30, 2014 at 12:41 PM, Stephan Beal <[email protected]>wrote:
> Because you've already made the commit and finfo with a filename works on > the current checkout version. That file isn't in your checkout, so it's > unknown. That's not very intuitive, but i don't currently see how fossil > could reasonably behave otherwise. > Perhaps a better error message, like say "file_a.ext does not exit in current working space". But then, why not look up the file in the repository even if it's not in the current working space? > History and full rename info is retained. i think you're just confused by > the finfo behaviour described above (which is arguable but would introduce > ambiguities and irregularities in results if it behaved differently). > Renamed files have been a problem in every VCS I've ever used, even hugely expensive commercial systems. Moved files even more so. Unfortunately, the only people I know who might be able to come up with a solution work for companies who consider projects like Fossil or Git as competitors, so their employment contracts prevent them from contributing.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
