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
On Mon, Sep 30, 2013 at 12:13 PM, Bob Archer wrote:
>>
>> But that has the effect that i will have all the changes from trunk in
>> branch A,
>> which is not what I want. I only want some certain changes inside there, the
>> changes committed from our team.
>>
>
> Common stuff should be brought i
On 9/30/13 10:13 AM, "Bob Archer" wrote:
>> 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,
> 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 thi
person will have to resolve those.
BOb
>
> Best Regards,
> Sven
>
> >
> >> -Original Message-
> >> From: Sven Richter [mailto:sver...@googlemail.com]
> >> Sent: 30 September 2013 13:29
> >> To: users@subversion.apache.org
> >>
> -Original Message-
> From: Sven Richter [mailto:sver...@googlemail.com]
> Sent: Monday, September 30, 2013 9:43 AM
> To: users@subversion.apache.org
> Subject: Re: Copy changes from one branch to another
>
> Hi,
>
>
>
> On Mon, Sep 30, 2013 at
Guten Tag Sven Richter,
am Montag, 30. September 2013 um 14:53 schrieben Sie:
> Well, the way has come a long way and to reproduce it would take me a
> lot of time so i would please you and the others to just take it as
> given.
That implies that your description is the best or maybe even only
so
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
> -Original Message-
> From: Sven Richter [mailto:sver...@googlemail.com]
> Sent: Monday, September 30, 2013 8:29 AM
> To: users@subversion.apache.org
> Subject: Copy changes from one branch to another
>
> Hi,
>
> I have the following setup
>
> tru
: users@subversion.apache.org
>> Subject: Copy changes from one branch to another
>>
>> Hi,
>>
>> I have the following setup
>>
>> trunk branch A (created from trunk)
>> | |
>> | |
>> | |
>>
avid.grier...@bskyb.com / Chatter: CBS SDLC Tools
Watermark Building, Alba Campus, Livingston, EH54 7HH
> -Original Message-
> From: Sven Richter [mailto:sver...@googlemail.com]
> Sent: 30 September 2013 13:29
> To: users@subversion.apache.org
> Subject: Copy changes from one
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
12 matches
Mail list logo
