{"thread":{"id":"47721","subject":"2.15.1 - merge with submodule output issue","startedAt":"2018-01-30T15:43:02Z","lastAt":"2018-01-30T22:02:18Z","messageCount":2,"participants":["FIGADERE, LAURENT","Stefan Beller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"337790","messageId":"DDD544204D3240408540BFCC028E06882F12F237@FRCRPVV9EX5MSX.ww931.my-it-solutions.net","threadId":"47721","inReplyTo":null,"subject":"2.15.1 - merge with submodule output issue","fromName":"FIGADERE, LAURENT","fromEmail":"laurent.figadere@atos.net","sentAt":"2018-01-30T15:42:49Z","receivedAt":"2018-01-30T15:43:02Z","isPatch":false,"sender":{"key":"laurent.figadere@atos.net","avatar":null},"body":"Dear git,\n\nI use since few weeks now git 2.15.1.\n\nI did few trials but please find here my outputs.\n\nTo reproduce:\nUse a top module git which include a submodule\nFirst step: from a work area, I changed selected version of submodule in master branch.\nThen git add + git commit + git push\n\tA new commit on master branch has been published on my origin repository with the version v1.2 of submodule\n\nSecond step: in my second workarea, I created a user branch mybranch, then selected another release of submodule\nI added the update and then commit in mybranch.\n\tA new commit with release v2.0 of submodule is in my last SHA1 of mybranch\n\nLast step: in the second workarea, in mybranch, I first run ‘git fetch’ and then ‘git merge origin/master’\nI got a CONFLICT message of course due to the 2 different versions of submodule.\nHere the message:\nwarning: Failed to merge submodule submodule (commits don't follow merge-base) \nAuto-merging submodule \nCONFLICT (submodule): Merge conflict in submodule \nAutomatic merge failed; fix conflicts and then commit the result. \n\nNow I thought that the command ‘git submodule’ provided an output with both versions of modules (local and remote).\nBut this is not the case in my environment:\n[15:20:10] $ git submodule status \nU0000000000000000000000000000000000000000 submodule\n\nAnd when I run the mergetool command I have this output:\n[14:54:41] $ git mergetool \nMerging: \nsubmodule \nSubmodule merge conflict for 'submodule': \n  {local}: submodule commit 08f86f2404d9f8f616262971a3127e69f39f9d11 \n  {remote}: submodule commit b3dd6fde4f02258b88ad0b2dba6474c126b499f7 \nUse (l)ocal or (r)emote, or (a)bort? \n\nSo, it means it’s not usefull to determine which version has to be selected.\nIs it a bug or perhaps I make something wrong?\n\nIt will be usefull if we can hav e this information during git mergetool command like with git describe .\n\nThanks for your help. \n\n\n-----------------------------\n\nLaurent FIGADERE\nCAD Engineer\nGBDS RD Asic Verification\n+33130805361\nlaurent.figadere@atos.net\nRue Jean Jaures BP 68\n78340 Les Clayes-sous-Bois\nFrance\nwww.Atos.net\n\n\n\nThis e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.\n\n\n\n\n"},{"id":"337847","messageId":"CAGZ79kab9oeZq4BJNBPaXA_uso3WQh_FBSE807E=ftBKvujsXQ@mail.gmail.com","threadId":"47721","inReplyTo":"DDD544204D3240408540BFCC028E06882F12F237@FRCRPVV9EX5MSX.ww931.my-it-solutions.net","subject":"Re: 2.15.1 - merge with submodule output issue","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2018-01-30T22:02:12Z","receivedAt":"2018-01-30T22:02:18Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Tue, Jan 30, 2018 at 7:42 AM, FIGADERE, LAURENT\n<laurent.figadere@atos.net> wrote:\n> Dear git,\n>\n> I use since few weeks now git 2.15.1.\n>\n> I did few trials but please find here my outputs.\n>\n> To reproduce:\n> Use a top module git which include a submodule\n> First step: from a work area, I changed selected version of submodule in master branch.\n> Then git add + git commit + git push\n>        A new commit on master branch has been published on my origin repository with the version v1.2 of submodule\n>\n> Second step: in my second workarea, I created a user branch mybranch, then selected another release of submodule\n> I added the update and then commit in mybranch.\n>        A new commit with release v2.0 of submodule is in my last SHA1 of mybranch\n>\n> Last step: in the second workarea, in mybranch, I first run ‘git fetch’ and then ‘git merge origin/master’\n> I got a CONFLICT message of course due to the 2 different versions of submodule.\n> Here the message:\n> warning: Failed to merge submodule submodule (commits don't follow merge-base)\n> Auto-merging submodule\n> CONFLICT (submodule): Merge conflict in submodule\n> Automatic merge failed; fix conflicts and then commit the result.\n>\n> Now I thought that the command ‘git submodule’ provided an output with both versions of modules (local and remote).\n> But this is not the case in my environment:\n> [15:20:10] $ git submodule status\n> U0000000000000000000000000000000000000000 submodule\n>\n> And when I run the mergetool command I have this output:\n> [14:54:41] $ git mergetool\n> Merging:\n> submodule\n> Submodule merge conflict for 'submodule':\n>   {local}: submodule commit 08f86f2404d9f8f616262971a3127e69f39f9d11\n>   {remote}: submodule commit b3dd6fde4f02258b88ad0b2dba6474c126b499f7\n> Use (l)ocal or (r)emote, or (a)bort?\n>\n> So, it means it’s not usefull to determine which version has to be selected.\n> Is it a bug or perhaps I make something wrong?\n\nIt's not a bug, but the real feature has not been implemented yet.\n"}]}