RE: [Subclipse-users] 1.1.4: Merge conflict during commit in freshly shared project

Sorry Mark,

        I didn't know that suggestions were not welcome here. I'll get
used to it, although I still don't understand what "versioning folders"
has to do with that...

========================================
Olavo Lira

-----Original Message-----
From: Mark Phippard [mailto:markp@softlanding.com]
Sent: Friday, July 28, 2006 10:58 AM
To: users@subclipse.tigris.org
Subject: RE: [Subclipse-users] 1.1.4: Merge conflict during commit in
freshly shared project

"LIRA Olavo" <Olavo.LIRA@gemalto.com> wrote on 07/28/2006 10:54:12 AM:

> Even though it's not a bug it is a very strange behavior that I
> would never expect. Normally if you shared the project that is no need
> for you to do a update after.

We cannot change Subversion, and the behavior really is not strange for
a
version control system that is going to version folders. There is no
way
that we are going to issue an automatic update after doing a commit so
it
would be best if you just get used to how Subversion works.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jul 28 17:07:28 2006