All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Tim Visher <tim.visher@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Print last time and committer a file was touched by for a whole repo
Date: Thu, 1 Jul 2010 14:40:36 -0700	[thread overview]
Message-ID: <20100701214035.GA2969@dcvr.yhbt.net> (raw)
In-Reply-To: <20100701200525.GA3686@burratino>

Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi Tim,
> 
> Tim Visher wrote:
> 
> > I need to get a listing of the entire contents of my current repo (as
> > in, I don't need deleted files or anything like that, just the current
> > snapshot) with the time the file was committed and who committed it.
> 
> You might be able to adapt Eric’s set-file-times script from [1].
> 
> The set-file-times script was designed to produce consistent
> Last-Modified headers when serving static content from a cluster of
> HTTP servers.  It does not do the right thing for merges (it is
> missing at least ‘-c’), though it will at least produce consistent
> results in that case.  See the wiki page for details.

Yes, "git log -c" is more correct, thanks.

I've brought http://yhbt.net/git-set-file-times back up and updated it.
(I changed servers for yhbt.net around 1.5 years ago and broke
a bunch of links I forgot existed).

Since the rsync developers distribute an outdated (and missing
disclaimer) version of this, perhaps we should just include this in the
contrib/ section of git.git...

-- 
Eric Wong

  reply	other threads:[~2010-07-01 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 19:05 Print last time and committer a file was touched by for a whole repo Tim Visher
2010-07-01 19:45 ` Eric Raible
2010-07-01 20:05 ` Jonathan Nieder
2010-07-01 21:40   ` Eric Wong [this message]
2010-07-02  3:37     ` Jonathan Nieder
2010-07-01 20:12 ` Jakub Narebski
2010-07-02 11:55   ` Tim Visher
2010-07-03  9:13     ` Jakub Narebski
2010-07-05  9:53       ` Jakub Narebski

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=20100701214035.GA2969@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=tim.visher@gmail.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.