zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Quick local CVS change scan, and bug in read?
Date: Sun, 19 May 2013 01:36:50 -0400	[thread overview]
Message-ID: <20130519053650.GA93384@redoubt.spodhuis.org> (raw)
In-Reply-To: <CAH+w=7bKhv8weLHcOJBonBc99joqGyGi_61uKjoWmkfjnwZadw@mail.gmail.com>

On 2013-05-18 at 21:26 -0700, Bart Schaefer wrote:
> Thanks.  Based on the discussion there, AIUI the hook sets the timestamp to
> the commit time?

Short version: yes, with some hand-waving to cover "what you meant" vs
"pedantic".

"git help show" and in "PRETTY FORMATS" the "format:<string>" section;
%ai/%at are the author timestamp; there's two timestamps, author and
committer, each of which can be overriden by env variables
($GIT_AUTHOR_DATE, $GIT_COMMITTER_DATE).

"commit time" changes if you rebase and is used for finding when
something happened in a particular branch's history.  "author time" is
when the change is recorded as having first been made.

So the patch updates the timestamps on the files to the time of the
commit which last modified those files (not the timestamps on the files
at the time that their changes were committed).

> Indeed it does, thanks for the archeology.

No problem.  "git blame" ("git annotate") is nice, and since it only has
to work locally it's blessedly fast.  (If you've ever dealt with
Perforce, you'll know how bad annotations can be ...)

-Phil


      reply	other threads:[~2013-05-19  5:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18 23:24 Bart Schaefer
2013-05-19  1:29 ` Phil Pennock
2013-05-19  4:26   ` Bart Schaefer
2013-05-19  5:36     ` Phil Pennock [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

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

  git send-email \
    --in-reply-to=20130519053650.GA93384@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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://git.vuxu.org/mirror/zsh/

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