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

Mark Phippard <markp@softlanding.com> wrote on 31.07.2006 15:09:53:

> Gunnar is not having a problem sharing the project, he is having a
problem
> with a change he makes after the share. Consider this scenario:

Yes, I understand all of it, I was just pointing out, that from the "User"
perspective, the "Share project" action is a single action, and that maybe
in that one scenario it would make sense to update the folder to Head.

I am of course talking about brand new users who have absolutely no
experience with Subversion itself, and are trying out Subclipse for the
first time. After that, of course you throw an error, if the user is
trying to go against how Subversion works.

> My point being that you are going to run into this problem no matter
what
> we do because that is how Subversion works and we cannot issue an update

> after every commit. Adding an update at the end of Share Project just
> does not seem like it is really fixing anything.

Exactly, you run into that sooner or later, but maybe in one specific
situation it could be later. It's not that I am not used to how Subversion
works, but I sort of see the point of view of a new and inexperienced
user.

Best regards,

---
  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org