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 235487
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T20:16:08+00:00 2026-05-11T20:16:08+00:00

I have merged in Subversion/TortoiseSVN like this a few times: Method A: 1) I

  • 0

I have merged in Subversion/TortoiseSVN like this a few times:

Method A:

  • 1) I change the trunk and commit.

  • 2) I make other changes in a branch and commit.

  • 3) In a working copy from trunk:
    I merge from the branch using TortoiseSVN’s
    ‘Merge a range of revisions’.

  • 4) Then I commit the trunk and delete the branch.

However, the
TortoiseSVN-manual recommends the following instead of 3) and 4):

Method B:

  • 3*) In a working copy from the branch:
    Merge changes from trunk using TortoiseSVN’s ‘Merge a range of revisions’.

  • 4*) Commit the branch including trunk changes.

  • 5*) In a working copy from the trunk:
    Merge changes from the branch using TortoiseSVN’s ‘Reintegrate a branch’.

  • 6*) Commit the trunk and delete the branch.

I find A much easier and have not found a reason why I shouldn’t do it like that.

What are the arguments for method B, or A,
when merging from a branch back to the trunk?

  • 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-05-11T20:16:08+00:00Added an answer on May 11, 2026 at 8:16 pm

    It is call “rebasing” before merging back: you “rebase” (or update) your local branch with trunk evolutions before merging back that local branch to trunk.

    It allows for slow resolution of the merge within your “a branch”, with possible intermediate commits.
    Then, when all is done, you can do a trivial merge back to trunk.
    That way, you do not have to delay commits only because you are merging on trunk (since only stable commits should be allowed on trunk).

    Would you consider it harmful to use approach ‘A’?

    No, if the merge is a trivial one, with a predictible result. In that case, approach B would be a waste of time, an extra merge which is not needed (and you should always seek to make as few merges as possible: each of those operations can be error-prone)

    But if the result is not well defined in advance, then approach ‘B’ is definitively recommended, and allows you to explore the result of the merge in your own branch, before impacting ‘trunk’.

    Both approaches are useful, one should not seek to apply only one or only the other, but the one most adapted to the situation at hand.

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

Sidebar

Related Questions

I may have found a Subversion bug, and I would like to make sure
Here's the situation: On a particular branch, some changes have been merged in from
I have some 100 files to be merged from one branch to the other.
I have a subversion repo with the following layout: svnrepo/projectA/trunk svnrepo/projectA/tags svnrepo/projectA/branches svnrepo/projectB/trunk svnrepo/projectB/tags
We are using Subversion and TortoiseSVN. We use the trunk for development and branches
Brought forward from Subversion feature branch requires changes from another feature branch I have
Does anyone have any experience with this? For instance, consider Subversion, Git, or Mercurial,
I have a subversion repository with the standard layout, i.e. trunk/ and branches/ (and
I have merged master into my bugXY branch, and needed to merge a file.
I have merged multiple jpeg files into one single .bin file. ..... ......... while(true){

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.