[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: LIRA Olavo <Olavo.LIRA_at_gemalto.com>
Date: 2006-07-28 17:39:14 CEST

Hi Mark,

        Sorry for the misunderstanding then, I should have been clearer.
I'm evaluating the current process of my company and modifying them, so
now we are using PVCS and I'm pushing to SVN but this is for sure one
question that may come up and I wouldn't know what to answer.
        Could you try to explain me or point me a document or a web page
where I can find a reason for this? I have the pdf of the Subversion
book but I couldn't find anything in there...
        Thanks in advance.

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

-----Original Message-----
From: Mark Phippard [mailto:markp@softlanding.com]
Sent: Friday, July 28, 2006 11:09 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 11:07:09 AM:

> 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...

They are welcome but there is really nothing we can do here. This is
how
Subversion works and it works this way for a reason. Also, you did not
make any suggestions, you just said it is confusing.

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:39:36 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.