[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RE: Re: Keeping last-modified dates

From: Thompson, Graeme (AELE) <Graeme.Thompson_at_smiths-aerospace.com>
Date: 2006-08-30 09:46:17 CEST

> -----Original Message-----
> From: Ian Brockbank [mailto:Ian.Brockbank@wolfsonmicro.com]
> Sent: 29 August 2006 15:20
> To: Mike Brenner; users@subversion.tigris.org
> Subject: RE: Re: Keeping last-modified dates
> Hi Mike,
> > Stability and debugging often depend on
> > having an original, unmodified file
> > for everything except the unit under test.
> >
> > We should evolve subversion towards
> > keeping the modified date.
> Conversely, if I'm trying to investigate a problem in an old
> version, I
> need to be able to roll back and play around with the old code. With
> subversion's current timestamp behaviour, I just need to update to the
> correct version and rebuild. If the timestamps were set to
> the check-in
> time or similar, Visual Studio would see that they were older than the
> object files and skip over them. I have wasted hours in the
> past trying
> to work out why my code wasn't doing what I expected only to find the
> code hadn't been rebuilt. Yes, in some ways trivial, but
> under pressure
> it's the simple things you miss.
> That's the issue subversion's current behaviour avoids. Fine, get it
> added as an option, but please don't force me to use it.

I think that adding it as an option is all that people are asking for!
Also to keep the current behaviour as default.

It is the case that there are a lot of people that are interested in the
modified date-time information for a variety of reasons, and the
argument seems to be that these people should never need the modified
time because it has been deemed useless.

In reality there is no defining reason to use any of the methodologies
on offer here, it simply comes down to personal preference, which I am
sure that everyone can agree that we will never get a consensus on!

Subversion should simply provide options to allow everyone to work how
they feel most comfortable.

It would be great if the trunk of subversion could already do this, but
unfortunately it is still work in progress.

See http://subversion.tigris.org/issues/show_bug.cgi?id=1256 for the
official bug about it.

And search the archives for "Getting Bug 1256 fixed" as there was a
recent (Nov 2005!) discussion about this, which was not the first
discussion on this subject.


The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 09:49:53 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.