On 23.02.2005, at 09:07, Ulrich Eckhardt wrote:
> Scott Palmer wrote:
>> 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.
This wouldn't help our case. We are a web design shop, creating web
sites for many different clients. Often PDFs or other content which is
supposed to appear on the web site will come directly from the client
by email. We most certainly will not be giving our clients write access
to our development repository; we'll accept the files by email and
check them in. And then we have the same problem Scott pointed out.
Commit time != modification time.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 24 15:42:25 2005