You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Thierry Robert <th...@gmail.com> on 2009/12/15 16:33:17 UTC
Re : need have a begin transaction on different branch
I have the same problem too.
I'm working in a company using subversion for its projects
I need to be able to lock folders on the repository before committing them
to avoid simultanous commits.
--
Thy
Re: need have a begin transaction on different branch
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Dec 15, 2009, at 10:33, Thierry Robert wrote:
> I need to be able to lock folders on the repository before committing them to avoid simultanous commits.
Why do you (or your management) think you need to do that? Have you tried just using Subversion the usual way? What problems have you run into with that?
Re: Re : need have a begin transaction on different branch
Posted by Guillaume <gu...@gmail.com>.
up ?
--
BADIN Guillaume
Appartement 405
2 promenade des sapeurs pompiers
94800 Villejuif
On Wed, Dec 16, 2009 at 9:16 AM, Guillaume <gu...@gmail.com> wrote:
>
> My problem is not on ACID Transaction, my problem is that we have 3
> different projects.
> These projects are dependent but are not in the same repository.
>
> ex :
> 3 projects A, B, C
>
> If I made modifications on A and B :
> - I commit A
> - Other developer commit its own modification of B
> - I cannot commit B (because of conflict)
> - The build is broken until I resolved B conflicts
>
> My needs are If I made modifications on A and B :
> - I lock A & B
> - I commit A
> - I commit B
> - I unlock A & B
> - Other developer commit its own modifications on project B
>
>
> --
> BADIN Guillaume
> Appartement 405
> 2 promenade des sapeurs pompiers
> 94800 Villejuif
>
>
> On Tue, Dec 15, 2009 at 6:38 PM, Bob Archer <Bo...@amsi.com> wrote:
>
>> > I have the same problem too.
>> > I'm working in a company using subversion for its projects
>> > I need to be able to lock folders on the repository before
>> > committing them to avoid simultanous commits.
>> >
>> > --
>> > Thy
>>
>> subversion commits are ACID transactions so simultaneous commits will not
>> cause any problems.
>>
>> If the file your are commiting isn't up to do svn will return an error.
>>
>> So, if you an I both submit a change to ^/foo.txt one of us will win the
>> other will get an error that foo.txt is out of date and you need to update
>> and commit again. When you update you will get either a clean merge or a
>> conflict. If a conflict you resolve it and then you can commit again.
>>
>
>
>> So, you really don't need to be able to lock folders to avoid simultaneous
>> commits.
>>
>> BOb
>>
>
>
>
>
>
Re: Re : need have a begin transaction on different branch
Posted by Guillaume <gu...@gmail.com>.
My problem is not on ACID Transaction, my problem is that we have 3
different projects.
These projects are dependent but are not in the same repository.
ex :
3 projects A, B, C
If I made modifications on A and B :
- I commit A
- Other developer commit its own modification of B
- I cannot commit B (because of conflict)
- The build is broken until I resolved B conflicts
My needs are If I made modifications on A and B :
- I lock A & B
- I commit A
- I commit B
- I unlock A & B
- Other developer commit its own modifications on project B
--
BADIN Guillaume
Appartement 405
2 promenade des sapeurs pompiers
94800 Villejuif
On Tue, Dec 15, 2009 at 6:38 PM, Bob Archer <Bo...@amsi.com> wrote:
> > I have the same problem too.
> > I'm working in a company using subversion for its projects
> > I need to be able to lock folders on the repository before
> > committing them to avoid simultanous commits.
> >
> > --
> > Thy
>
> subversion commits are ACID transactions so simultaneous commits will not
> cause any problems.
>
> If the file your are commiting isn't up to do svn will return an error.
>
> So, if you an I both submit a change to ^/foo.txt one of us will win the
> other will get an error that foo.txt is out of date and you need to update
> and commit again. When you update you will get either a clean merge or a
> conflict. If a conflict you resolve it and then you can commit again.
>
> So, you really don't need to be able to lock folders to avoid simultaneous
> commits.
>
> BOb
>
RE: Re : need have a begin transaction on different branch
Posted by Bob Archer <Bo...@amsi.com>.
> I have the same problem too.
> I'm working in a company using subversion for its projects
> I need to be able to lock folders on the repository before
> committing them to avoid simultanous commits.
>
> --
> Thy
subversion commits are ACID transactions so simultaneous commits will not cause any problems.
If the file your are commiting isn't up to do svn will return an error.
So, if you an I both submit a change to ^/foo.txt one of us will win the other will get an error that foo.txt is out of date and you need to update and commit again. When you update you will get either a clean merge or a conflict. If a conflict you resolve it and then you can commit again.
So, you really don't need to be able to lock folders to avoid simultaneous commits.
BOb