> From: Sander Striker [mailto:striker@apache.org]
> Sent: Friday, May 02, 2003 10:50
> To: Mark Watts; dev@subversion.tigris.org
>
> > From: Mark Watts [mailto:mwatts3@stny.rr.com]
> > Sent: Friday, May 02, 2003 4:45 PM
>
> > * As a user I find it very annoying that a check out (svn
> co) into a
> > new working directory leaves all files with the current date time
> > stamp. As a contractor I often have to merge files in from
> customers
> > source repositories in my local repository I use for their
> work. To
> > do this I do a fresh check out (svn co) from Subversion,
> then do the
> > equivalent of an update (most often a 'get') from their
> repository over the top of my working directory.
> > However, because I have done this subversion now thinks that most
> > files are up-to-date because the 'get' sets the timestamps
> of files to
> > a date in the past, usually the last date it was edited.
> This leaves me with something of
> > a mess. As it is right now I am going to have to write a
> small python
> > script that will create a database of the current date time
> stamps of
> > all the files in a particular revision, check that in and then on a
> > fresh checkout run the script to reset all the date time stamps to
> > their proper values. Quite the hack. Frankly, there may be some
> > better way to handle this situation that I am simply not
> aware of. If
> > so please point me in the right direction as I REALLY don't
> want to do
> > it this way but the other benefits of subversion are just
> too good to ignore.
>
> Simply 'touch' all the files you 'get' from the other end?
> All is well then.
Now, why didn't I think of that? Been too long a week. Thanks!
-Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 2 16:55:20 2003