On 13/08/2004, at 10:45 AM, Brian W. Fitzpatrick wrote:
> Wait, don't! There's a way to get around this--just check out a copy
> of your EOModel somewhere else, and copy the .svn directory into the
> eomodel with your changes in it. That way you don't have to redo your
> changes.
Yes, I thought of that after I had posted (it was late ...).
>
>>> Oh, and watch out in the future--I don't think EOModeler is .svn
>>> savvy.
>>
>> So why doesn't EOModeler just make a copy of the EOModel into the
>> backup copy rather than, as it would seem, moving the old model and
>> creating a new one!? (Rhetorical question)
>
> Because EOModeler is an old, sucky, crufty piece of software that
> should be taken out back and shot (Rhetorical answer).
>
> :-)
Sad but very true.
>> This seems very problematic for use with SVN?
>>
>> Is there any workaround ... I'm not sure how to "watch out" in this
>> situation?
>
> See above.
Ouch, that's not very nice at all. I guess that is what developers who
used CVS had to do as well (apart from using cvswrappers or similar).
Cheers,
Ashley.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 13 06:59:06 2004