I have a custom theme derived from cloudy. It's different enough that SVN has trouble merging, so I keep cloudy "clean" and have my variant in its own dir.
Once in a while, I go through diffs in cloudy and decide what I want to bring over. I did so yesterday, when cloudy/style.css was at 5485.
One of the changes I copied was putting "dot dot slash dot dot" on the beginning of a path near the end of the file.
Today, I noticed that the file had moved from 5485 to 5503, and I decided to go ahead and check. My SVN client is telling me that the change I had _already_ copied was made in 5503 today, NOT 5485 yesterday.
Now I would never pretend I am immune to mistakes. It's entirely possible for me to make a mistake and get the revision. BUT, what I copied, I copied from the SVN diffs view, and I did it _yesterday_ How can this be? (OK, I understand about time zones, too, but my time zone is minus five, and I did that before midnight last night, several hours before 5503 was committed.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am very confused by something.
I have a custom theme derived from cloudy. It's different enough that SVN has trouble merging, so I keep cloudy "clean" and have my variant in its own dir.
Once in a while, I go through diffs in cloudy and decide what I want to bring over. I did so yesterday, when cloudy/style.css was at 5485.
One of the changes I copied was putting "dot dot slash dot dot" on the beginning of a path near the end of the file.
Today, I noticed that the file had moved from 5485 to 5503, and I decided to go ahead and check. My SVN client is telling me that the change I had _already_ copied was made in 5503 today, NOT 5485 yesterday.
Now I would never pretend I am immune to mistakes. It's entirely possible for me to make a mistake and get the revision. BUT, what I copied, I copied from the SVN diffs view, and I did it _yesterday_ How can this be? (OK, I understand about time zones, too, but my time zone is minus five, and I did that before midnight last night, several hours before 5503 was committed.)
SVN 5503 was committed on Tuesday, so it was probably simply a problem with the timestamp in your svn client.