opensubscriber
   Find in this group all groups
 
Unknown more information…

o : offtopic@delphi.org.nz 5 October 2007 • 5:32AM -0400

RE: [DUG-Offtopic] Tortoise Shell SVN
by Conor Boyd

REPLY TO AUTHOR
 
REPLY TO GROUP




There is a checkbox in the TortoiseSVN settings dialog which allows you
to get TortoiseSVN to set file date to the last commit date/time, but I
think this isn't quite the same as your issue.

Personally, I think what you're experiencing is perfectly normal. Is it
causing problems for you?

If I can speak frankly, it feels slightly like you're viewing
TortoiseSVN as something of a backup strategy, rather than an inherent
part of your development process.  Maybe once you've completely
"committed" yourself (pun intended!) to TortoiseSVN, it will fade more
into the background.

TortoiseSVN just "works" for me.  I do an initial checkout, regular
updates to get stuff from other developers, regular commits when I've
finished a piece of work, and it just "works".

I think the way it sets dates is correct, so that Delphi will recompile
things as required when I do an update.

Cheers,

C.

-----Original Message-----
From: offtopic-bounces@delp...
[mailto:offtopic-bounces@delp...] On Behalf Of
johnkbird@para...

A query about Tortoise - I set it up to control some existing source,
and it is working fine, however all source files have been redated to be
the date and time of the first setup/update.  I would have preferred to
keep the existing dates.

Is this normal?

I suspect its to do with how I set up the original folder and repository
- its not completely obvious how to introduce Tortoise to an existing
source folder.

_______________________________________________
NZ Borland Developers Group Offtopic mailing list
Post: Offtopic@delp...
Admin: http://delphi.org.nz/mailman/listinfo/offtopic
Unsubscribe: send an email to offtopic-request@delp... with Subject: unsubscribe

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.