git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Lou, Pengfei (NSB - CN/Hangzhou)" <pengfei.lou@nokia-sbell.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: one bug on git
Date: Tue, 3 Dec 2019 09:08:40 +0000	[thread overview]
Message-ID: <a755356230794fb58bdd48dd74714aee@nokia-sbell.com> (raw)
In-Reply-To: <CAGyf7-FW_8RjVPEtmKiNFnF5QNZ4f+kqZ_BAGnGu76QcR=F25Q@mail.gmail.com>

Hi
   Thanks for your support
 
    But your idea was still not working as my wanted , please check the result below

[pelou@hzling29 try_des]$ git log -1 --raw --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15
commit 9d00cc608993840e24f65c7b79ae10f85c2d72ff
Author: pelou <pengfei.lou@nokia-sbell.com>
Date:   Tue Dec 3 17:00:47 2019 +0800

    2

:100644 100644 d474e1b... 9a7456b... M  lpf
[pelou@hzling29 try_des]$ git log --raw --no-walk=unsorted 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15^ 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15
commit 9d00cc608993840e24f65c7b79ae10f85c2d72ff
Author: pelou <pengfei.lou@nokia-sbell.com>
Date:   Tue Dec 3 17:00:47 2019 +0800

    2

:100644 100644 d474e1b... 9a7456b... M  lpf

commit 57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15
Author: pelou <pengfei.lou@nokia-sbell.com>
Date:   Tue Dec 3 17:00:47 2019 +0800

    3

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. 

tks
Br, Hercules

-----Original Message-----
From: Bryan Turner <bturner@atlassian.com> 
Sent: 2019年12月3日 16:56
To: Lou, Pengfei (NSB - CN/Hangzhou) <pengfei.lou@nokia-sbell.com>
Cc: git@vger.kernel.org
Subject: Re: one bug on git

On Tue, Dec 3, 2019 at 12:29 AM Lou, Pengfei (NSB - CN/Hangzhou) <pengfei.lou@nokia-sbell.com> wrote:
>
> Hello community
>      One problem I found recently within my working, please check my detail below.
>
>      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
>
> [pelou@hzling29 try_des]$ git --version git version 2.6.2
>
> [pelou@hzling29 try_des]$ git log --raw -1 
> 164304f48726d31336e2e130a90e42b7f1c480f8
> commit 164304f48726d31336e2e130a90e42b7f1c480f8
> Author: pelou <mailto:pengfei.lou@nokia-sbell.com>
> Date:   Tue Dec 3 14:54:33 2019 +0800
>
>     3
>
> :100644 100644 9a7456b... 8148ef7... M  lpf
> [pelou@hzling29 try_des]$ git log --raw -1 
> 164304f48726d31336e2e130a90e42b7f1c480f8^ 
> 164304f48726d31336e2e130a90e42b7f1c480f8
> commit dd1a95338ffd471e5b270a487b585bbfcf9926a5
> Author: pelou <mailto:pengfei.lou@nokia-sbell.com>
> Date:   Tue Dec 3 14:54:33 2019 +0800
>
>     2
>
> :100644 100644 d474e1b... 9a7456b... M  lpf
>
>      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
> [pelou@hzling29 try_des]$ git log --raw -1 
> 2027dc54da1896cf1dfa301c3444b1690d6cb1d8
> commit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8
> Author: pelou <mailto:pengfei.lou@nokia-sbell.com>
> Date:   Tue Dec 3 15:00:45 2019 +0800
>
>     3
>
> :100644 100644 9a7456b... 8148ef7... M  lpf
> [pelou@hzling29 try_des]$ git log --raw -1 
> 2027dc54da1896cf1dfa301c3444b1690d6cb1d8^ 
> 2027dc54da1896cf1dfa301c3444b1690d6cb1d8
> commit 2027dc54da1896cf1dfa301c3444b1690d6cb1d8
> Author: pelou <mailto:pengfei.lou@nokia-sbell.com>
> Date:   Tue Dec 3 15:00:45 2019 +0800
>
>     3
>
> :100644 100644 9a7456b... 8148ef7... M  lpf
>
> So please help me fix it. Please let me know if I was wrong or miss 
> some thing

By 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).

If 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.

Hope this helps,
Bryan Turner

[1] https://git-scm.com/docs/git-log#_commit_ordering

>
> Br, Hercules

  reply	other threads:[~2019-12-03  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <defeb7be75f54e8483ce529b2571478d@nokia-sbell.com>
2019-12-03  8:28 ` one bug on git Lou, Pengfei (NSB - CN/Hangzhou)
2019-12-03  8:29   ` Lou, Pengfei (NSB - CN/Hangzhou)
2019-12-03  8:56     ` Bryan Turner
2019-12-03  9:08       ` Lou, Pengfei (NSB - CN/Hangzhou) [this message]
2019-12-03  9:21         ` Bryan Turner
2019-12-03  9:25           ` Lou, Pengfei (NSB - CN/Hangzhou)
     [not found]             ` <CAGyf7-HmACw1im7C-RfkO5YLf0t+11LmqwPqMOjSTN5a4y7-hg@mail.gmail.com>
2019-12-03  9:30               ` Bryan Turner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a755356230794fb58bdd48dd74714aee@nokia-sbell.com \
    --to=pengfei.lou@nokia-sbell.com \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).