StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>By default, the date in <code>git log</code> will show in the default format.</p> <blockquote> <p>--date=default shows timestamps in the original timezone (either committer’s or author’s).</p> </blockquote> <p>Based on <a href="https://www.kernel.org/pub/software/scm/git/docs/git-log.html" rel="nofollow noreferrer">Git help log</a></p> <blockquote> <p>--date=local shows timestamps in user’s local timezone.</p> <p>--date=default shows timestamps in the original timezone (either committer’s or author’s).</p> </blockquote> <p>I suggest you run <code>git log --date=local --since=<your date></code>. It's supposed to show all commits in your local machine's time.</p> <p>Now, back to your question about <code>--since</code>.</p> <p>If <code>--since=<date></code> is without specific a time, it will use your local time <strong>at the time you run this command</strong>.</p> <p>For example,</p> <pre><code>--since "20-09-2013" </code></pre> <p>when you run this command at 09AM, will act as </p> <pre><code>--since "20-09-2013 09:00:00" </code></pre> <p>so, that's why it doesn't make some commits on that day show up. (because it already passed your current time)</p> <p>if you would like to search for all commits for today then use</p> <pre><code>--since "20-09-2013 00:00:00" </code></pre> <p><strong>back to mystery story</strong></p> <p>So, now <code>git log --since=19-09-2013.</code> That returns</p> <blockquote> <p>Date: Fri Sep 20 08:04:13 2013 +0200</p> <p>Date: Fri Sep 20 08:03:28 2013 +0200</p> <p>Date: Fri Sep 20 08:02:05 2013 +0200</p> <p>Date: Thu Sep 19 09:53:10 2013 +0200</p> </blockquote> <p>What I guess that you have run this command from 08:04:13 afterward on 20 Sep 2013. (Based on your hint that when you use <strong>since today</strong>, it shows nothing.).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload