git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Chris Frey <cdfrey@foursquare.net>
Cc: jidanni@jidanni.org, dhruvakm@gmail.com, git@vger.kernel.org
Subject: Re: timestamps not git-cloned
Date: Sat, 29 Nov 2008 10:22:31 +0100	[thread overview]
Message-ID: <20081129092231.GA32630@cuci.nl> (raw)
In-Reply-To: <20081129085406.GA20428@foursquare.net>

Chris Frey wrote:
>On Fri, Nov 28, 2008 at 01:06:00PM +0800, jidanni@jidanni.org wrote:
>> I hate it when I get some latest WhizBang.tgz, only to untar it to
>> find all the files' dates the same, when in fact the README hasn't
>> been touched in seven years, but you can't tell that from ls -l. I
>> recall some content tracker was involved.

>If this is the important bit, perhaps git-archive could be changed
>to create tarballs with file timestamps based on their commit dates.

Based on the principle of least surprise, I'd consider this a rather good
idea.
-- 
Sincerely,
           Stephen R. van den Berg.

To people that say "I could care less" - well, why don't you?

  reply	other threads:[~2008-11-29  9:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28  2:24 timestamps not git-cloned jidanni
2008-11-28  3:08 ` dhruva
2008-11-28  5:06   ` jidanni
2008-11-28  6:59     ` Daniel Barkalow
2008-11-29  8:54     ` Chris Frey
2008-11-29  9:22       ` Stephen R. van den Berg [this message]
2008-11-29 10:16         ` Thomas Rast
2008-11-30  0:48           ` jidanni
2008-12-01  9:09             ` Andreas Ericsson
2008-12-01 11:44               ` Jakub Narebski
2008-11-30  1:14           ` Sitaram Chamarty
2008-11-28  5:57   ` David Brown
2008-11-28 14:59   ` Peter Krefting
2008-11-28 11:51 ` Johannes Schindelin
2008-11-28 12:58 ` Robin Rosenberg
2008-11-28 13:20   ` Johannes Schindelin

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=20081129092231.GA32630@cuci.nl \
    --to=srb@cuci.nl \
    --cc=cdfrey@foursquare.net \
    --cc=dhruvakm@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jidanni@jidanni.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.
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).