Merging branch rev range into another branch
I've got a branch (b) that was made from another branch (a), and I wanted to merge a range of revisions from branch a to branch b, but I get to the following message:
Merging revisions 1654-2691 of http://xyz/svn/inetpub/branches/DevBranch into C:Branch, respecting ancestry
C:Branch
...
C:Branch
One or more conflicts were produced while merging r1777:1868 into
'C:Branch' --
resolve all conflicts and rerun the merge to apply the remaining
unmerged revisions
Any idea what this is about?
Afaict I have multiple conflicts on the same file and I need to resolve step by step, but that sounds awfully painful to a git user. Is there something I am missing? or is there a easier way to do this merge?
Thanks,
svn tortoise-svn
asked Dec 22 '11 at 22:39
ztaticztatic
265518
add a comment |
I've got a branch (b) that was made from another branch (a), and I wanted to merge a range of revisions from branch a to branch b, but I get to the following message:
Merging revisions 1654-2691 of http://xyz/svn/inetpub/branches/DevBranch into C:Branch, respecting ancestry
C:Branch
...
C:Branch
One or more conflicts were produced while merging r1777:1868 into
'C:Branch' --
resolve all conflicts and rerun the merge to apply the remaining
unmerged revisions
Any idea what this is about?
Afaict I have multiple conflicts on the same file and I need to resolve step by step, but that sounds awfully painful to a git user. Is there something I am missing? or is there a easier way to do this merge?
Thanks,
svn tortoise-svn
asked Dec 22 '11 at 22:39
ztaticztatic
265518
add a comment |
I've got a branch (b) that was made from another branch (a), and I wanted to merge a range of revisions from branch a to branch b, but I get to the following message:
Merging revisions 1654-2691 of http://xyz/svn/inetpub/branches/DevBranch into C:Branch, respecting ancestry
C:Branch
...
C:Branch
One or more conflicts were produced while merging r1777:1868 into
'C:Branch' --
resolve all conflicts and rerun the merge to apply the remaining
unmerged revisions
Any idea what this is about?
Afaict I have multiple conflicts on the same file and I need to resolve step by step, but that sounds awfully painful to a git user. Is there something I am missing? or is there a easier way to do this merge?
Thanks,
svn tortoise-svn
asked Dec 22 '11 at 22:39
ztaticztatic
265518
I've got a branch (b) that was made from another branch (a), and I wanted to merge a range of revisions from branch a to branch b, but I get to the following message:
Merging revisions 1654-2691 of http://xyz/svn/inetpub/branches/DevBranch into C:Branch, respecting ancestry
C:Branch
...
C:Branch
One or more conflicts were produced while merging r1777:1868 into
'C:Branch' --
resolve all conflicts and rerun the merge to apply the remaining
unmerged revisions
Any idea what this is about?
Afaict I have multiple conflicts on the same file and I need to resolve step by step, but that sounds awfully painful to a git user. Is there something I am missing? or is there a easier way to do this merge?
Thanks,
svn tortoise-svn
svn tortoise-svn
asked Dec 22 '11 at 22:39
ztaticztatic
265518
asked Dec 22 '11 at 22:39
ztaticztatic
265518
asked Dec 22 '11 at 22:39
ztaticztatic
265518
asked Dec 22 '11 at 22:39
ztaticztatic
265518
asked Dec 22 '11 at 22:39
ztaticztatic
265518
265518
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
svn merge command is sensitive to ancestry. This means when you are trying to merge any set of changes (from a branch, from trunk, from anything) the order is preserved and svn tries to merge changes one-by-one. This is mostly nice, you just simulate every little change occurs in branches, thus nothing is lost. Every time svn is stuck due to high number of conflicts it stops and asks you to resolve the conflicts before merge is resumed.
If two branches are isolated, are not merged (synchronized) often and are kept in this state for a long time (as in your case) this behavior is really painfull. You can just ignore the ancestry (versions between branching and HEAD) and do a simpler merge by using the flag --ignore-ancestry. This way merge determines the differences to be merged just as svn diff determines the differences between two versions, without considering ancestry.
Note that you should examine your merged working copy and be sure that everything is as you want them to be, since ignoring ancestry also ignores some of the changes made on the way, but did not make to latest version.
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f370816%2fmerging-branch-rev-range-into-another-branch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
svn merge command is sensitive to ancestry. This means when you are trying to merge any set of changes (from a branch, from trunk, from anything) the order is preserved and svn tries to merge changes one-by-one. This is mostly nice, you just simulate every little change occurs in branches, thus nothing is lost. Every time svn is stuck due to high number of conflicts it stops and asks you to resolve the conflicts before merge is resumed.
If two branches are isolated, are not merged (synchronized) often and are kept in this state for a long time (as in your case) this behavior is really painfull. You can just ignore the ancestry (versions between branching and HEAD) and do a simpler merge by using the flag --ignore-ancestry. This way merge determines the differences to be merged just as svn diff determines the differences between two versions, without considering ancestry.
Note that you should examine your merged working copy and be sure that everything is as you want them to be, since ignoring ancestry also ignores some of the changes made on the way, but did not make to latest version.
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
add a comment |
svn merge command is sensitive to ancestry. This means when you are trying to merge any set of changes (from a branch, from trunk, from anything) the order is preserved and svn tries to merge changes one-by-one. This is mostly nice, you just simulate every little change occurs in branches, thus nothing is lost. Every time svn is stuck due to high number of conflicts it stops and asks you to resolve the conflicts before merge is resumed.
If two branches are isolated, are not merged (synchronized) often and are kept in this state for a long time (as in your case) this behavior is really painfull. You can just ignore the ancestry (versions between branching and HEAD) and do a simpler merge by using the flag --ignore-ancestry. This way merge determines the differences to be merged just as svn diff determines the differences between two versions, without considering ancestry.
Note that you should examine your merged working copy and be sure that everything is as you want them to be, since ignoring ancestry also ignores some of the changes made on the way, but did not make to latest version.
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
add a comment |
svn merge command is sensitive to ancestry. This means when you are trying to merge any set of changes (from a branch, from trunk, from anything) the order is preserved and svn tries to merge changes one-by-one. This is mostly nice, you just simulate every little change occurs in branches, thus nothing is lost. Every time svn is stuck due to high number of conflicts it stops and asks you to resolve the conflicts before merge is resumed.
If two branches are isolated, are not merged (synchronized) often and are kept in this state for a long time (as in your case) this behavior is really painfull. You can just ignore the ancestry (versions between branching and HEAD) and do a simpler merge by using the flag --ignore-ancestry. This way merge determines the differences to be merged just as svn diff determines the differences between two versions, without considering ancestry.
Note that you should examine your merged working copy and be sure that everything is as you want them to be, since ignoring ancestry also ignores some of the changes made on the way, but did not make to latest version.
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
svn merge command is sensitive to ancestry. This means when you are trying to merge any set of changes (from a branch, from trunk, from anything) the order is preserved and svn tries to merge changes one-by-one. This is mostly nice, you just simulate every little change occurs in branches, thus nothing is lost. Every time svn is stuck due to high number of conflicts it stops and asks you to resolve the conflicts before merge is resumed.
If two branches are isolated, are not merged (synchronized) often and are kept in this state for a long time (as in your case) this behavior is really painfull. You can just ignore the ancestry (versions between branching and HEAD) and do a simpler merge by using the flag --ignore-ancestry. This way merge determines the differences to be merged just as svn diff determines the differences between two versions, without considering ancestry.
Note that you should examine your merged working copy and be sure that everything is as you want them to be, since ignoring ancestry also ignores some of the changes made on the way, but did not make to latest version.
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
answered Jan 25 '12 at 12:49
infiniteRefactorinfiniteRefactor
740514
740514
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f370816%2fmerging-branch-rev-range-into-another-branch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
