On Feb 22, 2005, at 10:22 AM, Scott Palmer wrote:
>
> The use-case that comes up here is for .pdf files or other content
> generated by non-programmers who do not directly use subversion. They
> hand a file over to the engineering team to incorporate into a build.
> On their own computers they have their own organization of the files
> and talk in terms of when they last updated the file, not when the
> engineering team decided to commit it to subversion. When I have to
> answer something along the lines of, "Did you get the changes I made
> last Thursday?" I can't go by the commit time that shows the
> following Monday because that isn't a strong enough indicator that I
> have Thursday's changes. Maybe I got an update on Wednesday and
> that's what I committed. If the timestamp (and size, etc.) matched
> exactly with the file that the creator has, I'm pretty confident that
> we are talking about the same thing.
Wow, that's really clear. Thanks for that explanation and example.
Maybe you should come persuade folks over on dev@ to increase the
priority and work out the implementation of this feature.
There's already an issue #1256 patch, but it needs a lot more attention
and discussion. (I'm tied up working on the locking feature right
now.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 22 17:39:38 2005