This is a a follow on to ticket 1015:
I have raised a new ticket since it appears that this is a separate problem which I mentioned in the original ticket and a follow-up when the original ticket was fixed (thanks Chris!).
However the second part of issue 1015 is still not fixed/consistent.
There is a bit of diagnosis below...
Looking at the top screen of the NetInf Code page as of a few moments ago (changeset 127)
I see that the VERSION file was 'updated 23 hours ago'. That is correct, but the README file, which was updated at much the same time, says that it was modified at '2012-03-20'. Well, yes it was, but that was the date when the project was created and the README has been updated several times since. Looking through the tree there are many
example where the last modified time was project creation time but that is not the case in reality.
Looking at this a little more closely, it looks as if any file that existed when the project was originally created (such as the top level README) exhibits the data and commit log from the project creation event, but files (such as VERSION) which were added to the project subsequently exhibit the correct modification time and last commit log.
Thus many of the files in the 'ruby' directory show 2012-03-20 seemingly because they existed at project creation time, but in most cases have been modified since, whereas all the files in the python/nilib directory all show the correct time and commit log entry - these files were created (or more accurately moved) in the last week because the Python code got reorganized.
Is this a smoking gun?
Log in to post a comment.