up ?
--
BADIN Guillaume
Appartement 405
2 promenade des sapeurs pompiers
94800 Villejuif
On Wed, Dec 16, 2009 at 9:16 AM, Guillaume 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 reposit
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 commi
> 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
a
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 ru
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
Hello everybody I work in a company where we develop on 3 projects in same
time, the 3 projects are under subversion and are not in the same
repository.
My problem is when we commit modifications on 2 or 3 projects we can break
the build.
My questions are :
- Can we lock an entire project with
