Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8283219
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T10:39:31+00:00 2026-06-08T10:39:31+00:00

I have a strange tree conflict when integrating revisions into a working copy and

  • 0

I have a strange tree conflict when integrating revisions into a working copy and I do not understand why … 🙁

The development is done in /trunk/project.
Revision 619 was branched to /branches/divB/majorwork in order to implement major changes. In parallel, working in trunk continued.
In revision 636 the branch was re-integrated into the trunk. svn:mergeinfo of “project” got the entry

/branches/divB/majorwork:620-635

Finally, in revision 680, a stable tag was created in /tags/v1.0

Now the HEAD is Rev 706 and I want to create /tags/v1.1 with just a small bugfixes backported to v1.0. The revisions I want to merge from trunk are 682-683.

Now I do the following:
1.) svn switch from my working copy to /tags/v1.0
2.) svn merge revisions 682-683 from /trunk/project into working copy.

However, intead that the small set of files is merged into my working copy, I get a tree conflict on the main directory “project”: When I choose “Check for modifications”, I get:

Path      Text status             Property status
---------+-----------------------+----------------
project   normal                  modified
project   missing, tree conflict

When I compare the “project” folder, I find that:

svn:mergeinfo : Working base:

/branches/divB/majorwork:620-635

svn:mergeinfo : Working copy

/branches/divB/majorwork:620-635
/trunk:682-683

I do not understand why I get a tree conflict here and what I am doing wrong. My intention was to merge the text files which have changed and then tag the working copy to /tags/v1.1

Can anyone explain?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T10:39:33+00:00Added an answer on June 8, 2026 at 10:39 am

    Sorry I was really too dumb and missed the forest for the trees …

    I did merge from /trunk rather than /trunk/project …

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

i have strange behaviour of git - push is working, but clone is not
I have strange error and not sure how to tackle it without wasting too
I am looking into a strange problem where a JBoss 4.2.2 server is not
i have strange problem , my application (exe) is working fine in debug mode
i have strange problem doing reporting: i have numerous clients with different issued invoices.
I have strange behaviour in Python/PyMongo. dbh = self.__connection__['test'] first = dbh['test_1'] second =
I have strange problem with receiving data from socket. On client im using air
I tried to draw a model with 197 polygons but i have strange black
I know it's a simple question, but I have strange behaviour in here. <pre>
I have a strange problem on ipv6 connection. I write down a simple client

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.