Branch is updating file modification times, but shouldn't.

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Dave Schulte
Posts: 55
Joined: Thu Dec 02, 2004 1:59 pm

Branch is updating file modification times, but shouldn't.

Post by Dave Schulte » Mon Dec 20, 2004 1:47 pm

We have found that doing a "branch from label" causes not only the revision for every file associated with the label to have its revision number increased, but also to have the file's modification time as recorded in Vault changed to equal the time of the branch.

This is BAD!

It is ok to increase the revision number to associate a new history point to show that the file was branched from some previous revision. It is even ok to change the file's checkin date/time, even though the file image did not change (i.e., a new phyiscal image was not checked in -- some might argue that even this is NOT ok). However, Vault should NEVER change a file's modification time if a new image was not physically checked in. We are loosing the fact of when the file was physically changed last.

jclausius
Posts: 3655
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Dec 20, 2004 1:55 pm

This is the current design of Vault, and this was discussed a short time ago - Modified dates on branched files

If you would like, I can make a feature request for a design change.
Jeff Clausius
SourceGear

Dave Schulte
Posts: 55
Joined: Thu Dec 02, 2004 1:59 pm

Post by Dave Schulte » Mon Dec 20, 2004 1:57 pm

Yes, we would prefer this be changed or at least an option to support retaining modification times on branch.

jclausius
Posts: 3655
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Dec 20, 2004 2:03 pm

No problem.

I've created a feature request in your name.
Jeff Clausius
SourceGear

Post Reply