If you want to store the modification date as part of the commit and you
don't mind really mucking with the repository, you could somehow back-date
the commit so that it matches the modification date of the file involved
(edit the dump file?)
----- Original Message -----
From: "Charles Doucette" <charles.doucette@synxis.com>
To: "Max Bowsher" <maxb@ukf.net>
Cc: <users@subversion.tigris.org>
Sent: Thursday, September 16, 2004 4:25 PM
Subject: RE: Re: Subversion erase original date of files ??
> -----Original Message-----
> From: Max Bowsher [mailto:maxb@ukf.net]
> Sent: Thursday, September 16, 2004 6:58 PM
> To: Charles Doucette
> Cc: users@subversion.tigris.org
> Subject: Re: Re: Subversion erase original date of files ??
>
>
> Charles Doucette wrote:
> > I realize that I can write hook scripts to save/restore the
> original
> > file modification times; but,
> > a) I don't think I should have to
> > (I believe this behavior should be built-in - perhaps
> via a built-in
> > attribute)
> > b) I believe there are other people who desire this behavior besides
> > myself.
>
> Yes, but only a small minority, none of whom have actually
> stepped forward
> to attempt to design a concrete way to conditionalize this
> behaviour (which
> would be highly detrimental to the common case of
> 'make'-built software
> projects), and then to write some code.
>
> Max.
>
>
Touche! That's the best response I've heard yet.
I agree that my desire to maintain the modification dates is not
necessary,
and could potentially be detrimental (some files may not get rebuilt
that should),
and therefore a) shouldn't be the default behavior, and b) isn't high
priority.
I thought if enough people agreed with me that I could enlist the expert
developers
to design and build it for me/us. But, I can understand and agree with
put up or shut up -
esp. for open source code. So, I guess I'll shut up.
Chuck
p.s. One scenario that I've come across where this behavior is
desirable
is when you download or inherit someone else's project. You want
the modification
dates to reflect the modification dates of the original/last
maintainer
(or the last source control system), and not to be changed
unless you change/modify the file.
In place import for one developer solves this problem. It would
be nice if any other
developers could automatically have an equal (not equivalent)
working copy with
the original modification dates too.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 17 01:37:07 2004