git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Turner <bturner@atlassian.com>
To: "Lou, Pengfei (NSB - CN/Hangzhou)" <pengfei.lou@nokia-sbell.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: one bug on git
Date: Tue, 3 Dec 2019 01:21:51 -0800	[thread overview]
Message-ID: <CAGyf7-Fn-XRQhGCLdr+WxBAWKywQH2_s8XCsNUG7Vpgyu2jjUg@mail.gmail.com> (raw)
In-Reply-To: <a755356230794fb58bdd48dd74714aee@nokia-sbell.com>

On Tue, Dec 3, 2019 at 1:08 AM Lou, Pengfei (NSB - CN/Hangzhou)
<pengfei.lou@nokia-sbell.com> wrote:
>
> 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

At 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^
(9d00cc608993840e24f65c7b79ae10f85c2d72ff) and
57cf56b8c1af9115a7f8e1c1c8f07e4d657e8b15--in the order you asked for
them.

What output are you _expecting_ to see?

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

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

Bryan

>
> tks
> Br, Hercules

P.S. Please don't top-post on the list. Respond inline adjacent to the
part of the message you're talking about.

  reply	other threads:[~2019-12-03  9:22 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)
2019-12-03  9:21         ` Bryan Turner [this message]
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

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

  git send-email \
    --in-reply-to=CAGyf7-Fn-XRQhGCLdr+WxBAWKywQH2_s8XCsNUG7Vpgyu2jjUg@mail.gmail.com \
    --to=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=pengfei.lou@nokia-sbell.com \
    /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.
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 NNTP newsgroup(s).