Zsh Mailing List Archive
Messages sorted by:
Re: Quick local CVS change scan, and bug in read?
- X-seq: zsh-workers 31414
- From: Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Quick local CVS change scan, and bug in read?
- Date: Sun, 19 May 2013 01:36:50 -0400
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201210; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=OJ4/EmB+/dqyahmDCmn7aYyu4sq7WgQnOLDGc5lxkGg=; b=umRLHFxQ2gG9ABKTF5fpr6XuGc+WTnPn4vGaaUtjUTLCGBQzCO6xR9bUbwslT/FfXCnqsUv7vWeTYQNncOWoXjxc8fPiQLTr7zhuE/ClsfhTOrTwgTalxErAhuavohX3ZkN5paIqfn5OwLtX3DiaACyhcyGXjvQsP0qHu2iDrUE=;
- In-reply-to: <CAH+w=7bKhv8weLHcOJBonBc99joqGyGi_61uKjoWmkfjnwZadw@mail.gmail.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mail-followup-to: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAH+w=7YQLJZGxjdA=ZwA_u+JJg=LcGPRkPExj5bNcXRhX6hZUg@mail.gmail.com> <20130519012902.GA83443@redoubt.spodhuis.org> <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
"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
"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 ...)
Messages sorted by: