All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Kulikov <dima@koulikoff.ru>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git log --since=<date>
Date: Sat, 02 May 2020 07:54:03 +0200	[thread overview]
Message-ID: <42953119.Wv2erQna2g@hp470> (raw)
In-Reply-To: <xmqqd07nl3dt.fsf@gitster.c.googlers.com>

On Friday 01 May 2020 15:03:10 Junio C Hamano wrote:

> Dmitry Kulikov <dima@koulikoff.ru> writes:
> > I have found a problem.
> > 
> > It turned out, that the timestamp used to determinate which commit is
> > later
> > the given date is not at 0h 0m 0s, Instead it is at the current time.
> > 
> > Similarly --until=<date> uses not 23h 59m 59s but also current time.
> 
> The behaviour is as designed.  "git log --since=yesterday" does the
> same "as nobody said which hour and minute, we take it to mean this
> time yesterday".

  In the documentation it is not described this way. It is said:

       --since=<date>, --after=<date>
           Show commits more recent than a specific date.

  Nothing is said about the time I entered the command.

> You of course can say "git log --since=yesterday.midnight" if you
> want to be exact ;-).

  What should I enter instead --since=2020-05-01 to have a midnight time?

-- 

With best regards,
   Dmitry Kulikov

mailto:dima@koulikoff.ru
skype: dima.koulikoff
phone: +49 151 6338 5032
Viber, WhatsApp: +7 925 505 2185

  reply	other threads:[~2020-05-02  5:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 21:35 git log --since=<date> Dmitry Kulikov
2020-05-01 22:03 ` Junio C Hamano
2020-05-02  5:54   ` Dmitry Kulikov [this message]
2020-05-02 11:03     ` Danh Doan
2020-05-02 11:52       ` Dmitry Kulikov
2020-05-02 16:21       ` Junio C Hamano
2020-05-02 12:02     ` Dmitry Kulikov

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=42953119.Wv2erQna2g@hp470 \
    --to=dima@koulikoff.ru \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.