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.
Subversion is not a programmers' tool, although primarily used by programmers.
> 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.
There is a solution to this, and this is how I do it here:
- teach them (non-programmers) versioning basics (e.g. the advantage of being
able to backtrack changes)
- give them a toy repository to play with
- beat them to use versioning and then only take files that are in their
repository, not files edited by $foo and sent by mail or somesuch.
I believe it was worth it, YMMV.
> 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.
I think you see how these problems dissolve to nothing with above approach.
good luck!
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 23 09:07:51 2005