Eric Wong <normalperson@xxxxxxxx> wrote: > Junio C Hamano <gitster@xxxxxxxxx> wrote: > > * I've seen t9119-git-svn-info.sh fail in my k.org private repository > > and have been skipping the test, but this needs to be diagnosed and > > fixed [*1*]. It could be just that the code is fine and the test is > > not rejecting SVN that is too-old. I dunno. > > I wouldn't mind dropping this test for now. > > 100% output compatibility with SVN is too difficult to achieve > and IMHO not worth it for commands like `info' and `log'. > > David: > > I also noticed some race-conditions on this test when running this on my > Centrino laptop (my fastest box, but I rarely use it for git > development) and having git on my USB thumb drive. I'm pretty sure > these were caused by inconsistencies in handling timestamps on symlinks > vs timestamps on the files they link to. The problem is that 'svn info' is reading the mtime from its hidden backup file (in the .svn directory) instead of the file in the working directory, so setting the mtime (and atime) of the git working copy file using the svn working copy doesn't always work. I'm working on a solution now. Dave - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
