>
> On Apr 19, 2010, at 03:53, ja...@smars.pl wrote:
>
>> Ok, it seems to be ok but has some disadvantages:
>>
>> when I commit changes on either trunk, this change is made only on
>> /share/module_1234 (the revision number of project1 or project2 will not
>> increase).
>> Because of the above th
script)
>> - create some script on server side? (hooks, no script would be needed
>> on
>> developer side, but could it be done using hooks???)
>> how such hook (probably post-commit) would looks like?
>> svn update project2
>> svn merge -c $REV http://svn/project1/trunk/module_1234
>> svn commit -m "" project2
>>
>> ???
>>
>> - any other?
>>
>>
>> Best Regards
>> Jacek
>>
>>
>>
>
could it be done using hooks???)
how such hook (probably post-commit) would looks like?
svn update project2
svn merge -c $REV http://svn/project1/trunk/module_1234
svn commit -m "" project2
???
- any other?
Best Regards
Jacek