On 28 November 2012 14:01, Derek Hansen <derek.hansen_at_chiefind.com> wrote:
> Hello everyone,
> I am very green when it comes to version control and the company I work for has decided they would like to implement it.
> So in my research I feel that using subversion is going to be our best way to go about doing things.
> I have installed TortoiseSVN and for the most part have been finding my way around it. However in my effort to "work it out" I am coming across difficulties with the merge process. No matter what it seems I do a conflict does not appear to arise.
> I have attached all the steps that I took in order to attempt to get an understanding of how it works.
> In a nutshell though:
> 1) Create repository
> 2) Add files
> 3) Commit files
> 4) Create branch (switching to branch working copy)
> 5) Change branch (try to force a conflict)
> 6) Commit branch
> 7) Switch to trunk working copy
7a) At this point you need to change the same line in trunk but to
7b) Commit to trunk.
> 8) Merge (no conflicts arise)
> I have been staring at section 4.20 in the TortoiseSVN manual for way to long now and have come to hope that someone will be able to see what I am doing wrong.
A conflict arises when you change the same line in both places but in
different ways AFTER creating the branch. You cannot create a conflict
by changing something in the branch alone. A conflict arises when
different changes are made to the same lines in both trunk and branch
and Subversion cannot know which one you want to use.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-28 15:28:57 CET