From: Junio C Hamano <gitster@pobox.com>
To: Todd Lewis <utoddl@email.unc.edu>
Cc: git@vger.kernel.org
Subject: Re: bug report: dates on diff
Date: Thu, 06 Jul 2017 11:05:44 -0700 [thread overview]
Message-ID: <xmqq7ezlfnk7.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqbmoxfnns.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Thu, 06 Jul 2017 11:03:35 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Imagine this scenario:
>
> - Contributor A writes a change on 2017-07-01 and send it in to me
> - Contributor B writes a change on 2017-07-03 and send it in to me
> - I apply change from B on 2017-07-04 on 'master'
> - I apply change from A on 2017-07-05 on 'master'
> - You clone the resulting repository from me on 2017-07-06
>
> Now, you have at the tip of 'master' in your repository the commit
> that records the change by contributor A.
>
> And there are three times that are relevant to your tip of 'master'.
>
> - When was the commit that sits at the tip of 'master' made?
> - When was the change recorded in that commit made?
> - When was the commit made at the tip of _your_ 'master'?
>
> and the answers are 2017-07-01, 2017-07-05 and 2017-07-06, respectively.
> They are called "committer", "author" and "reflog" timestamps.
Oops, obviously the dates have to be 2017-07-05, 2017-07-01 and
2017-07-06. I made the commit on the 5th (i.e. "committer"
timestamp) that records a change written on the 1st (i.e. "author"
timestamp).
prev parent reply other threads:[~2017-07-06 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 12:54 bug report: dates on diff Todd Lewis
2017-07-06 16:22 ` Junio C Hamano
2017-07-06 17:32 ` Todd Lewis
2017-07-06 18:03 ` Junio C Hamano
2017-07-06 18:05 ` Junio C Hamano [this message]
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=xmqq7ezlfnk7.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=utoddl@email.unc.edu \
/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).