From: "Sitaram Chamarty" <sitaramc@gmail.com>
To: "Thomas Rast" <trast@student.ethz.ch>
Cc: "Stephen R. van den Berg" <srb@cuci.nl>,
"Chris Frey" <cdfrey@foursquare.net>,
jidanni@jidanni.org, dhruvakm@gmail.com, git@vger.kernel.org
Subject: Re: timestamps not git-cloned
Date: Sun, 30 Nov 2008 06:44:38 +0530 [thread overview]
Message-ID: <2e24e5b90811291714s4388289bwa4b2e22ff1f75a83@mail.gmail.com> (raw)
In-Reply-To: <200811291117.01655.trast@student.ethz.ch>
On Sat, Nov 29, 2008 at 3:46 PM, Thomas Rast <trast@student.ethz.ch> wrote:
> Stephen R. van den Berg wrote:
>> Chris Frey wrote:
>> >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.
>
> Unless I'm missing something, this would make git-archive rather more
> expensive than it is now: Tree objects do not record any timestamps,
How many people use git-archive and how many times a day do they use
it? For example, kernel.org seems to put out linux-2.x.y.z.tar.bz2
once every 2 to 7 days.
The overhead of this new option (and certainly it should be an option,
not the default) should be measured not against the old running time,
but against the frequency of usage of the tool. Look at it on those
time scales, it may not be a big deal.
By all accounts, this overhead will not affect the "giterate" [meaning
git-literate ;-)] people too much.
next prev parent reply other threads:[~2008-11-30 1:18 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
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 [this message]
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=2e24e5b90811291714s4388289bwa4b2e22ff1f75a83@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=cdfrey@foursquare.net \
--cc=dhruvakm@gmail.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.org \
--cc=srb@cuci.nl \
--cc=trast@student.ethz.ch \
/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).