Tim Hill wrote:
> Agreed. I'd be really scared about pushing changes out like this. You
> will be creating all sorts of odd merge situations. The correct place
> to handle this stuff is on the way *into* the repo, at commit time.
>
> What is the workflow that needs this kind of operation?
>
> --TIm
>
> Barry Gershenfeld wrote:
>>
>>> I've been thrust into SVN and immediately given a task.
>>> 1) When a local folder has been updated via SVN, an email is sent
>>> out. 2) An SVN update is then triggered facility wide.
>>
>> So one person makes a change, and it immediately changes for
>> everybody? What they are asking for sounds like a shared network drive.
>> No svn
>> needed...
Shared network drives..... Have problems, such as when the network is down
or in performance dealing with local file systems. Is there any way to use
an "rsync -e ssh -avvH" step, rather than a pushed update?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 20 05:27:31 2006