# RE: git merge deletes my changes 4 messages from 2016-10-10 to 2016-10-12. Participants: Eduard Egorov, Paul Smith, Jakub Narębski. Thread: https://gitlist.dev/t/44270 ## Eduard Egorov, 2016-10-10 10:19 Subject: RE: git merge deletes my changes Message-ID: URL: https://gitlist.dev/e/AM4PR03MB1636EA0DEB4C8095F04AB92ADBDB0%40AM4PR03MB1636.eurprd03.prod.outlook.com In-Reply-To: ``` Hello again, I've noticed that my git is quite old (1.8.3) and built it from source tarball (2.10.1). Now the output is: # ~/gitbuild/git-2.10.1/git merge -s subtree --squash ceph_ansible fatal: refusing to merge unrelated histories I've checked my command history again: 738 git rm -rf ceph-ansible/ 739 ll 740 ll ceph-ansible/ 741 rm ceph-ansible/purge_ceph_cluster.yml 742 git read-tree --prefix=ceph-ansible/ -u ceph_ansible 743 gs 744 gc "ceph-ansible: reset repo state" A quick googling showed (http://stackoverflow.com/questions/37937984/git-refusing-to-merge-unrelated-histories ) that the default behavior is changed. Adding ' --allow-unrelated-histories' clears the error message but the merge itself is still wrong (my changes are lost). This error message might explain why git can't merge it correctly (since these repos doesn't has any relations, right). Can somebody confirm this please? Doesn't "merge -s subtree" really merges branches? With best regards Eduard Egorov -----Original Message----- From: Eduard Egorov Sent: Monday, October 10, 2016 12:39 PM To: 'git@vger.kernel.org' Subject: git merge deletes my changes Hello Git experts, A week ago, I've reset a state of 'ceph-ansible' folder in %current% branch with code from corresponding branch (that tracks an upstream from github): # git read-tree --prefix=ceph-ansible/ -u ceph_ansible Then I've committed several changes, including: 1. Renamed file and commited: # git mv site.yml.sample site.yml 2. Made some changes and committed 3. Pulled updates from original branch by: # git merge -s subtree --squash ceph_ansible It said: Auto-merging ceph-ansible/site.yml.sample blablabla Squash commit -- not updating HEAD Automatic merge went well; stopped before committing as requested I can see that "my" ceph-ansible/site.yml is deleted (as well as few new files added by me), ceph-ansible/site.yml.sample is restored and doesn't contain my changes (it's just restored to the state before my changes). `git log ceph_ansible site.yml.sample` shows the latest change on ceph_ansible branch done from 26th of August, 2016, my changes in %current% branch was this October, so it shouldn't be any conflict either (even if it was). I believe there is some obvious explanation for this behavior. Could you help me please? What information can I provide in order to troubleshoot this issue? A post on SO: http://stackoverflow.com/questions/39954265/git-merge-deletes-my-changes With best regards Eduard Egorov ``` ## Paul Smith, 2016-10-10 17:52 Subject: Re: git merge deletes my changes Message-ID: <1476121942.15746.99.camel@mad-scientist.net> URL: https://gitlist.dev/e/1476121942.15746.99.camel%40mad-scientist.net In-Reply-To: ``` On Mon, 2016-10-10 at 10:19 +0000, Eduard Egorov wrote: > # ~/gitbuild/git-2.10.1/git merge -s subtree --squash ceph_ansible > > Can somebody confirm this please? Doesn't "merge -s subtree" really > merges branches? I think possibly you're not fully understanding what the --squash flag does... that's what's causing your issue here, not the "-s" option. A squash merge takes the commits that would be merged from the origin branch and squashes them into a single patch and applies them to the current branch as a new commit... but this new commit is not a merge commit (that is, when you look at it with "git show" etc. the commit will have only one parent, not two--or more--parents like a normal merge commit). Basically, it's syntactic sugar for a diff plus patch operation plus some Git goodness wrapped around it to make it easier to use. But ultimately once you're done, Git has no idea that this new commit has any relationship whatsoever to the origin branch.  So the next time you merge, Git doesn't know that there was a previous merge and it will try to merge everything from scratch rather than starting at the previous common merge point. So either you'll have to use a normal, non-squash merge, or else you'll have to tell Git by hand what the previous common merge point was (as Jeff King's excellent email suggests).  Or else, you'll have to live with this behavior. ``` ## Jakub Narębski, 2016-10-11 15:56 Subject: Re: git merge deletes my changes Message-ID: <94ff5fb3-6957-8983-4aa7-e1d5e2692e82@gmail.com> URL: https://gitlist.dev/e/94ff5fb3-6957-8983-4aa7-e1d5e2692e82%40gmail.com In-Reply-To: <1476121942.15746.99.camel@mad-scientist.net> ``` W dniu 10.10.2016 o 19:52, Paul Smith pisze: > On Mon, 2016-10-10 at 10:19 +0000, Eduard Egorov wrote: >> # ~/gitbuild/git-2.10.1/git merge -s subtree --squash ceph_ansible >> >> Can somebody confirm this please? Doesn't "merge -s subtree" really >> merges branches? > > I think possibly you're not fully understanding what the --squash flag > does... that's what's causing your issue here, not the "-s" option. > > A squash merge takes the commits that would be merged from the origin > branch and squashes them into a single patch and applies them to the > current branch as a new commit... but this new commit is not a merge > commit (that is, when you look at it with "git show" etc. the commit > will have only one parent, not two--or more--parents like a normal merge > commit). > > Basically, it's syntactic sugar for a diff plus patch operation plus > some Git goodness wrapped around it to make it easier to use. Actually this is full merge + commit surgery (as if you did merge with --no-commit, then deleted MERGE_HEAD); the state of worktree is as if it were after a merge. > > But ultimately once you're done, Git has no idea that this new commit > has any relationship whatsoever to the origin branch. So the next time > you merge, Git doesn't know that there was a previous merge and it will > try to merge everything from scratch rather than starting at the > previous common merge point. > > So either you'll have to use a normal, non-squash merge, or else you'll > have to tell Git by hand what the previous common merge point was (as > Jeff King's excellent email suggests). Or else, you'll have to live > with this behavior. The `git subtree` command (from contrib) allows yet another way: it squashes *history* of merged subproject (as if with interactive rebase 'squash'), then merges this squash commit. Now I know why this feature is here... -- Jakub Narębski ``` ## Eduard Egorov, 2016-10-12 05:51 Subject: RE: git merge deletes my changes Message-ID: URL: https://gitlist.dev/e/AM4PR03MB1636DC3017FFA1DE57BAABADDBDD0%40AM4PR03MB1636.eurprd03.prod.outlook.com In-Reply-To: <94ff5fb3-6957-8983-4aa7-e1d5e2692e82@gmail.com> ``` Hello Jakub, Thank you for addition. Eventually, I've merged your explanations into single answer post (http://stackoverflow.com/questions/39954265/git-merge-s-subtree-works-incorrectly/ ). I hope this will prevent other confused people from disturbing you by similar emails on this mailing list. This is another time I can evidence the power and flexibility the git provides, thank you all for your great work! With best regards Eduard Egorov -----Original Message----- From: Jakub Narębski [mailto:jnareb@gmail.com] Sent: Tuesday, October 11, 2016 6:57 PM To: Paul Smith; Eduard Egorov; 'git@vger.kernel.org' Subject: Re: git merge deletes my changes W dniu 10.10.2016 o 19:52, Paul Smith pisze: > On Mon, 2016-10-10 at 10:19 +0000, Eduard Egorov wrote: >> # ~/gitbuild/git-2.10.1/git merge -s subtree --squash ceph_ansible >> >> Can somebody confirm this please? Doesn't "merge -s subtree" really >> merges branches? > > I think possibly you're not fully understanding what the --squash flag > does... that's what's causing your issue here, not the "-s" option. > > A squash merge takes the commits that would be merged from the origin > branch and squashes them into a single patch and applies them to the > current branch as a new commit... but this new commit is not a merge > commit (that is, when you look at it with "git show" etc. the commit > will have only one parent, not two--or more--parents like a normal > merge commit). > > Basically, it's syntactic sugar for a diff plus patch operation plus > some Git goodness wrapped around it to make it easier to use. Actually this is full merge + commit surgery (as if you did merge with --no-commit, then deleted MERGE_HEAD); the state of worktree is as if it were after a merge. > > But ultimately once you're done, Git has no idea that this new commit > has any relationship whatsoever to the origin branch. So the next > time you merge, Git doesn't know that there was a previous merge and > it will try to merge everything from scratch rather than starting at > the previous common merge point. > > So either you'll have to use a normal, non-squash merge, or else > you'll have to tell Git by hand what the previous common merge point > was (as Jeff King's excellent email suggests). Or else, you'll have > to live with this behavior. The `git subtree` command (from contrib) allows yet another way: it squashes *history* of merged subproject (as if with interactive rebase 'squash'), then merges this squash commit. Now I know why this feature is here... -- Jakub Narębski ```