{"thread":{"id":"52381","subject":"RE: one bug on git","startedAt":"2019-12-03T08:29:02Z","lastAt":"2019-12-03T09:31:09Z","messageCount":7,"participants":["Lou, Pengfei (NSB - CN/Hangzhou)","Bryan Turner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"387431","messageId":"5e27e2a9f6374742859b4b87d85c56e9@nokia-sbell.com","threadId":"52381","inReplyTo":"defeb7be75f54e8483ce529b2571478d@nokia-sbell.com","subject":"RE: one bug on git","fromName":"Lou, Pengfei (NSB - CN/Hangzhou)","fromEmail":"pengfei.lou@nokia-sbell.com","sentAt":"2019-12-03T08:28:58Z","receivedAt":"2019-12-03T08:29:02Z","isPatch":false,"sender":{"key":"pengfei.lou@nokia-sbell.com","avatar":null},"body":"Hello community \n     One problem I found recently within my working, please check my detail below. \n\n     I tried to run my script (check the attached file 'problem.sh') to build one git repository , it can be successful, but the command \"git log -raw -1 ${revision}^ ${revision}\" on that repo would generate some  unexpected result,  please check the result below\n\n[pelou@hzling29 try_des]$ git --version\ngit version 2.6.2\n\n[pelou@hzling29 try_des]$ git log --raw -1 164304f48726d31336e2e130a90e42b7f1c480f8\ncommit 164304f48726d31336e2e130a90e42b7f1c480f8\nAuthor: pelou \nDate:   Tue Dec 3 14:54:33 2019 +0800\n\n    3\n\n:100644 100644 9a7456b... 8148ef7... M  lpf\n[pelou@hzling29 try_des]$ git log --raw -1 164304f48726d31336e2e130a90e42b7f1c480f8^ 164304f48726d31336e2e130a90e42b7f1c480f8\ncommit dd1a95338ffd471e5b270a487b585bbfcf9926a5\nAuthor: pelou \nDate:   Tue Dec 3 14:54:33 2019 +0800\n\n    2\n\n:100644 100644 d474e1b... 9a7456b... M  lpf \n\n     Next step I changed my script(check the attached file good.sh) and only add some delays after \"git push\", everything is normal, check it below\n[pelou@hzling29 try_des]$ git log --raw -1 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\ncommit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\nAuthor: pelou \nDate:   Tue Dec 3 15:00:45 2019 +0800\n\n    3\n\n:100644 100644 9a7456b... 8148ef7... M  lpf\n[pelou@hzling29 try_des]$ git log --raw -1 2027dc54da1896cf1dfa301c3444b1690d6cb1d8^ 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\ncommit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\nAuthor: pelou \nDate:   Tue Dec 3 15:00:45 2019 +0800\n\n    3\n\n:100644 100644 9a7456b... 8148ef7... M  lpf\n\nSo please help me fix it. Please let me know if I was wrong or miss some thing\n\nBr, Hercules\n"},{"id":"387432","messageId":"1af00173f96243bea760baaddeb15777@nokia-sbell.com","threadId":"52381","inReplyTo":"5e27e2a9f6374742859b4b87d85c56e9@nokia-sbell.com","subject":"RE: one bug on git","fromName":"Lou, Pengfei (NSB - CN/Hangzhou)","fromEmail":"pengfei.lou@nokia-sbell.com","sentAt":"2019-12-03T08:29:31Z","receivedAt":"2019-12-03T08:29:55Z","isPatch":false,"sender":{"key":"pengfei.lou@nokia-sbell.com","avatar":null},"body":"Hello community \n     One problem I found recently within my working, please check my detail below. \n\n     I tried to run my script (check the attached file 'problem.sh') to build one git repository , it can be successful, but the command \"git log -raw -1 ${revision}^ ${revision}\" on that repo would generate some  unexpected result,  please check the result below\n\n[pelou@hzling29 try_des]$ git --version\ngit version 2.6.2\n\n[pelou@hzling29 try_des]$ git log --raw -1 164304f48726d31336e2e130a90e42b7f1c480f8\ncommit 164304f48726d31336e2e130a90e42b7f1c480f8\nAuthor: pelou \nDate:   Tue Dec 3 14:54:33 2019 +0800\n\n    3\n\n:100644 100644 9a7456b... 8148ef7... M  lpf\n[pelou@hzling29 try_des]$ git log --raw -1 164304f48726d31336e2e130a90e42b7f1c480f8^ 164304f48726d31336e2e130a90e42b7f1c480f8\ncommit dd1a95338ffd471e5b270a487b585bbfcf9926a5\nAuthor: pelou \nDate:   Tue Dec 3 14:54:33 2019 +0800\n\n    2\n\n:100644 100644 d474e1b... 9a7456b... M  lpf \n\n     Next step I changed my script(check the attached file good.sh) and only add some delays after \"git push\", everything is normal, check it below\n[pelou@hzling29 try_des]$ git log --raw -1 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\ncommit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\nAuthor: pelou \nDate:   Tue Dec 3 15:00:45 2019 +0800\n\n    3\n\n:100644 100644 9a7456b... 8148ef7... M  lpf\n[pelou@hzling29 try_des]$ git log --raw -1 2027dc54da1896cf1dfa301c3444b1690d6cb1d8^ 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\ncommit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\nAuthor: pelou \nDate:   Tue Dec 3 15:00:45 2019 +0800\n\n    3\n\n:100644 100644 9a7456b... 8148ef7... M  lpf\n\nSo please help me fix it. Please let me know if I was wrong or miss some thing\n\nBr, Hercules\n"},{"id":"387433","messageId":"CAGyf7-FW_8RjVPEtmKiNFnF5QNZ4f+kqZ_BAGnGu76QcR=F25Q@mail.gmail.com","threadId":"52381","inReplyTo":"1af00173f96243bea760baaddeb15777@nokia-sbell.com","subject":"Re: one bug on git","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2019-12-03T08:56:16Z","receivedAt":"2019-12-03T08:56:29Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"On Tue, Dec 3, 2019 at 12:29 AM Lou, Pengfei (NSB - CN/Hangzhou)\n wrote:\n>\n> Hello community\n> One problem I found recently within my working, please check my detail below.\n>\n> I tried to run my script (check the attached file 'problem.sh') to build one git repository , it can be successful, but the command \"git log -raw -1 ${revision}^ ${revision}\" on that repo would generate some unexpected result, please check the result below\n>\n> [pelou@hzling29 try_des]$ git --version\n> git version 2.6.2\n>\n> [pelou@hzling29 try_des]$ git log --raw -1 164304f48726d31336e2e130a90e42b7f1c480f8\n> commit 164304f48726d31336e2e130a90e42b7f1c480f8\n> Author: pelou \n> Date: Tue Dec 3 14:54:33 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n> [pelou@hzling29 try_des]$ git log --raw -1 164304f48726d31336e2e130a90e42b7f1c480f8^ 164304f48726d31336e2e130a90e42b7f1c480f8\n> commit dd1a95338ffd471e5b270a487b585bbfcf9926a5\n> Author: pelou \n> Date: Tue Dec 3 14:54:33 2019 +0800\n>\n> 2\n>\n> :100644 100644 d474e1b... 9a7456b... M lpf\n>\n> Next step I changed my script(check the attached file good.sh) and only add some delays after \"git push\", everything is normal, check it below\n> [pelou@hzling29 try_des]$ git log --raw -1 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> commit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> Author: pelou \n> Date: Tue Dec 3 15:00:45 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n> [pelou@hzling29 try_des]$ git log --raw -1 2027dc54da1896cf1dfa301c3444b1690d6cb1d8^ 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> commit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> Author: pelou \n> Date: Tue Dec 3 15:00:45 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n>\n> So please help me fix it. Please let me know if I was wrong or miss some thing\n\nBy default, git log sorts commits by their timestamps and outputs them\nin reverse chronological order (as stated in the git log\ndocumentation[1]), not the order you requested the commits in. Without\nthe delays, the commits can happen so fast you end up with identical\ntimestamps on each commit. I'm not sure git log has a tie-breaker in\nsuch a case (it may just end up being input order).\n\nIf you want the commits to be output in the order you ask for them in,\nyou might try something like \"git log --raw --no-walk=unsorted sha^\nsha\". This will output exactly the commits you ask for (so \"sha\"'s\nfirst parent and \"sha\") in the same order you requested them in.\n\nHope this helps,\nBryan Turner\n\n[1] https://git-scm.com/docs/git-log#_commit_ordering\n\n>\n> Br, Hercules\n"},{"id":"387434","messageId":"a755356230794fb58bdd48dd74714aee@nokia-sbell.com","threadId":"52381","inReplyTo":"CAGyf7-FW_8RjVPEtmKiNFnF5QNZ4f+kqZ_BAGnGu76QcR=F25Q@mail.gmail.com","subject":"RE: one bug on git","fromName":"Lou, Pengfei (NSB - CN/Hangzhou)","fromEmail":"pengfei.lou@nokia-sbell.com","sentAt":"2019-12-03T09:08:40Z","receivedAt":"2019-12-03T09:08:44Z","isPatch":false,"sender":{"key":"pengfei.lou@nokia-sbell.com","avatar":null},"body":"Hi\n Thanks for your support\n \n But your idea was still not working as my wanted , please check the result below\n\n[pelou@hzling29 try_des]$ git log -1 --raw --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\ncommit 9d00cc608993840e24f65c7b79ae10f85c2d72ff\nAuthor: pelou \nDate: Tue Dec 3 17:00:47 2019 +0800\n\n 2\n\n:100644 100644 d474e1b... 9a7456b... M lpf\n[pelou@hzling29 try_des]$ git log --raw --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\ncommit 9d00cc608993840e24f65c7b79ae10f85c2d72ff\nAuthor: pelou \nDate: Tue Dec 3 17:00:47 2019 +0800\n\n 2\n\n:100644 100644 d474e1b... 9a7456b... M lpf\n\ncommit 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\nAuthor: pelou \nDate: Tue Dec 3 17:00:47 2019 +0800\n\n 3\n\nSo you mean it is not one bug /issue, and adding delay was mandatory for this case? Actually , I found it was still be failure if the delay was set 0.5 seconds. \n\ntks\nBr, Hercules\n\n-----Original Message-----\nFrom: Bryan Turner \nSent: 2019年12月3日 16:56\nTo: Lou, Pengfei (NSB - CN/Hangzhou) \nCc: git@vger.kernel.org\nSubject: Re: one bug on git\n\nOn Tue, Dec 3, 2019 at 12:29 AM Lou, Pengfei (NSB - CN/Hangzhou) wrote:\n>\n> Hello community\n> One problem I found recently within my working, please check my detail below.\n>\n> I tried to run my script (check the attached file 'problem.sh') \n> to build one git repository , it can be successful, but the command \n> \"git log -raw -1 ${revision}^ ${revision}\" on that repo would generate \n> some unexpected result, please check the result below\n>\n> [pelou@hzling29 try_des]$ git --version git version 2.6.2\n>\n> [pelou@hzling29 try_des]$ git log --raw -1 \n> 164304f48726d31336e2e130a90e42b7f1c480f8\n> commit 164304f48726d31336e2e130a90e42b7f1c480f8\n> Author: pelou \n> Date: Tue Dec 3 14:54:33 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n> [pelou@hzling29 try_des]$ git log --raw -1 \n> 164304f48726d31336e2e130a90e42b7f1c480f8^ \n> 164304f48726d31336e2e130a90e42b7f1c480f8\n> commit dd1a95338ffd471e5b270a487b585bbfcf9926a5\n> Author: pelou \n> Date: Tue Dec 3 14:54:33 2019 +0800\n>\n> 2\n>\n> :100644 100644 d474e1b... 9a7456b... M lpf\n>\n> Next step I changed my script(check the attached file good.sh) \n> and only add some delays after \"git push\", everything is normal, check \n> it below\n> [pelou@hzling29 try_des]$ git log --raw -1 \n> 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> commit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> Author: pelou \n> Date: Tue Dec 3 15:00:45 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n> [pelou@hzling29 try_des]$ git log --raw -1 \n> 2027dc54da1896cf1dfa301c3444b1690d6cb1d8^ \n> 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> commit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8\n> Author: pelou \n> Date: Tue Dec 3 15:00:45 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n>\n> So please help me fix it. Please let me know if I was wrong or miss \n> some thing\n\nBy default, git log sorts commits by their timestamps and outputs them in reverse chronological order (as stated in the git log documentation[1]), not the order you requested the commits in. Without the delays, the commits can happen so fast you end up with identical timestamps on each commit. I'm not sure git log has a tie-breaker in such a case (it may just end up being input order).\n\nIf you want the commits to be output in the order you ask for them in, you might try something like \"git log --raw --no-walk=unsorted sha^ sha\". This will output exactly the commits you ask for (so \"sha\"'s first parent and \"sha\") in the same order you requested them in.\n\nHope this helps,\nBryan Turner\n\n[1] https://git-scm.com/docs/git-log#_commit_ordering\n\n>\n> Br, Hercules\n"},{"id":"387435","messageId":"CAGyf7-Fn-XRQhGCLdr+WxBAWKywQH2_s8XCsNUG7Vpgyu2jjUg@mail.gmail.com","threadId":"52381","inReplyTo":"a755356230794fb58bdd48dd74714aee@nokia-sbell.com","subject":"Re: one bug on git","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2019-12-03T09:21:51Z","receivedAt":"2019-12-03T09:22:03Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"On Tue, Dec 3, 2019 at 1:08 AM Lou, Pengfei (NSB - CN/Hangzhou)\n wrote:\n>\n> Hi\n> Thanks for your support\n>\n> But your idea was still not working as my wanted , please check the result below\n>\n> [pelou@hzling29 try_des]$ git log -1 --raw --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> commit 9d00cc608993840e24f65c7b79ae10f85c2d72ff\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 2\n>\n> :100644 100644 d474e1b... 9a7456b... M lpf\n> [pelou@hzling29 try_des]$ git log --raw --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> commit 9d00cc608993840e24f65c7b79ae10f85c2d72ff\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 2\n>\n> :100644 100644 d474e1b... 9a7456b... M lpf\n>\n> commit 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 3\n\nAt this point I'm not sure what you're looking for. Your first command\nhas -1 on it, so it only prints the commit for\n57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^, which is\n9d00cc608993840e24f65c7b79ae10f85c2d72ff. Your second command omits\nthe -1 and so it prints both 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^\n(9d00cc608993840e24f65c7b79ae10f85c2d72ff) and\n57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15--in the order you asked for\nthem.\n\nWhat output are you _expecting_ to see?\n\n>\n> So you mean it is not one bug /issue, and adding delay was mandatory for this case? Actually , I found it was still be failure if the delay was set 0.5 seconds.\n\ngit commit records timestamps with second precision, so a delay of\nhalf a second means you can still have 2 commits recorded with\nidentical _to the second_ timestamps.\n\nBryan\n\n>\n> tks\n> Br, Hercules\n\nP.S. Please don't top-post on the list. Respond inline adjacent to the\npart of the message you're talking about.\n"},{"id":"387436","messageId":"0b2bd41ca3b34369ba0504e3bd7254ae@nokia-sbell.com","threadId":"52381","inReplyTo":"CAGyf7-Fn-XRQhGCLdr+WxBAWKywQH2_s8XCsNUG7Vpgyu2jjUg@mail.gmail.com","subject":"RE: one bug on git","fromName":"Lou, Pengfei (NSB - CN/Hangzhou)","fromEmail":"pengfei.lou@nokia-sbell.com","sentAt":"2019-12-03T09:25:30Z","receivedAt":"2019-12-03T09:25:54Z","isPatch":false,"sender":{"key":"pengfei.lou@nokia-sbell.com","avatar":null},"body":"I think it should be like below\n[pelou@hzling29 try_des]$ git log --raw -1 --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\ncommit 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\nAuthor: pelou \nDate: Tue Dec 3 17:00:47 2019 +0800\n\n 3\n\n:100644 100644 9a7456b... 8148ef7... M lpf\n\nBr, Hercules\n-----Original Message-----\nFrom: Bryan Turner \nSent: 2019年12月3日 17:22\nTo: Lou, Pengfei (NSB - CN/Hangzhou) \nCc: git@vger.kernel.org\nSubject: Re: one bug on git\n\nOn Tue, Dec 3, 2019 at 1:08 AM Lou, Pengfei (NSB - CN/Hangzhou) wrote:\n>\n> Hi\n> Thanks for your support\n>\n> But your idea was still not working as my wanted , please check \n> the result below\n>\n> [pelou@hzling29 try_des]$ git log -1 --raw --no-walk=unsorted \n> 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ \n> 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> commit 9d00cc608993840e24f65c7b79ae10f85c2d72ff\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 2\n>\n> :100644 100644 d474e1b... 9a7456b... M lpf\n> [pelou@hzling29 try_des]$ git log --raw --no-walk=unsorted \n> 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ \n> 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> commit 9d00cc608993840e24f65c7b79ae10f85c2d72ff\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 2\n>\n> :100644 100644 d474e1b... 9a7456b... M lpf\n>\n> commit 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 3\n\nAt this point I'm not sure what you're looking for. Your first command has -1 on it, so it only prints the commit for 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^, which is 9d00cc608993840e24f65c7b79ae10f85c2d72ff. Your second command omits the -1 and so it prints both 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^\n(9d00cc608993840e24f65c7b79ae10f85c2d72ff) and 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15--in the order you asked for them.\n\nWhat output are you _expecting_ to see?\n\n>\n> So you mean it is not one bug /issue, and adding delay was mandatory for this case? Actually , I found it was still be failure if the delay was set 0.5 seconds.\n\ngit commit records timestamps with second precision, so a delay of half a second means you can still have 2 commits recorded with identical _to the second_ timestamps.\n\nBryan\n\n>\n> tks\n> Br, Hercules\n\nP.S. Please don't top-post on the list. Respond inline adjacent to the part of the message you're talking about.\n"},{"id":"387437","messageId":"CAGyf7-FWF_-H=z9jozeoC05XDKTmzU2N4K5cH0WCdZnKBF8Osg@mail.gmail.com","threadId":"52381","inReplyTo":"CAGyf7-HmACw1im7C-RfkO5YLf0t+11LmqwPqMOjSTN5a4y7-hg@mail.gmail.com","subject":"Re: one bug on git","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2019-12-03T09:30:56Z","receivedAt":"2019-12-03T09:31:09Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"> On Tue, Dec 3, 2019 at 1:25 AM Lou, Pengfei (NSB - CN/Hangzhou) wrote:\n>\n> I think it should be like below\n> [pelou@hzling29 try_des]$ git log --raw -1 --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> commit 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\n> Author: pelou \n> Date: Tue Dec 3 17:00:47 2019 +0800\n>\n> 3\n>\n> :100644 100644 9a7456b... 8148ef7... M lpf\n\nSo you always want to see the child before the parent?\n\nTry \" git log --raw -1 --date-order\n57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^\n57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15\"\n\n(Replacing --no-walk=unsorted with --date-order)\n\nBryan\n\nP.S. Again, please don't top-post on the list.\n"}]}