On Mar 29, 2007, at 8:06 AM, Mark Phippard wrote:
> On 3/29/07, Jens Seidel <jensseidel@users.sf.net> wrote:
> Hi,
>
> I noticed that subclipse uses the (modification) time stamp of the
> affected file on the server when updating files. This results in files
> with a future time stamp on my system which confuses make. Subversion
> (svn update) uses the local host time instead.
>
> I use Linux, SVNKit, Subclipse 1.2.0 and eclipse 3.3M5eh.
>
> Should I open a bug report?
>
> Subclipse does not touch your files. Subversion does it via the
> API call (such as update) that we make. Subversion has two options
> here. The default is to set the time to current time. You can
> modify this via the config file in ~/.subversion to "Use-commit-time".
Another way of getting into this situation can be through use of a
network file share for storing the working copy, where the
workstation and the file server have time skew. That story would
cause the temporal discontinuity even from the command line, so your
report would appear to rule this out, but setting up these confirming
experiments can be darned finicky, depending on things like the
magnitude of the skew, so if you are in fact using such a set-up, it
might be worth confirming that your command-line experiment really
was equivalent to the Subclipse one.
-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: 844.7461
aim: jackrepenning
skype: jrepenning
Received on Thu Mar 29 18:15:46 2007