Hi,
thank you all for your input. I guess we are on the right track now.
Thinking about what you said we will go the different way, instead of
committing to branch A, the testsystem that should use branch A will
pull all changes from the trunk. If there is a merge error we can
handle this manually
Hi,
On Mon, Sep 30, 2013 at 3:14 PM, Andrew Reedick
wrote:
>
> Post commit script that deletes branch A and then recreates branch A from
> trunk, i.e. make branch A effectively a tag. Since the delete and copy are
> server side commands, no workspace is needed to make it work. However this
d we do have to run tests against both branches to make sure it
works with the different dependencies.
Does that make sense?
Best Regards,
Sven
>
>> -Original Message-
>> From: Sven Richter [mailto:sver...@googlemail.com]
>> Sent: 30 September 2013 13:29
>> To
Hi,
I have the following setup
trunk branch A (created from trunk)
| |
| |
| |
Now, what I want to do is only commit my changes to the trunk and make
sure that every committed change is replicated into branch A. This
should be an automatic commit, trigger
