From: jidanni@jidanni•org
To: git@vger•kernel.org
Subject: Re: timestamps not git-cloned
Date: Sun, 30 Nov 2008 08:48:41 +0800 [thread overview]
Message-ID: <87k5am3uom.fsf@jidanni.org> (raw)
In-Reply-To: 200811291117.01655.trast@student.ethz.ch
Well all I know is from the simple user who does e.g.,
# aptitude install linux-doc-2.6.26
# ls -lt /usr/share/doc/linux-doc-2.6.26/Documentation/
he thinks "gosh, can't tell what's new vs. what hasn't changed in years".
OK, now I know why this is tolerable upstream: they all use git.
But for the lowly user downstream who gets what git-archive produces,
it seems like a step backwards: "who threw away the timestamp of when
each file was last changed?".
OK, http://git.or.cz/gitwiki/ContentLimitations says this is by design.
And OK, thinking "file by file" is old fashioned, I read. The non-git
end user should just get used to reading ChangeLogs, if any, and stop
doing ls -lt.
But you must admit, /usr/share/doc/linux-doc-2.6.26/Documentation/
etc. are aimed for reading without git.
Anyways, if just in case any individual file modification time
information can still be pried from the 40 byte IDs or whatever, I
would suggest using it by default in git-archive at least, and maybe
even git-clone etc.
Just letting you know my 'valuable first impressions'. I expect once I
start smoking more of this "git" stuff, I too will become comfortably
numb to aforementioned lowly user problem, so you would never know
unless I hereby first told you before it was too late.
next prev parent reply other threads:[~2008-11-30 0:50 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 [this message]
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=87k5am3uom.fsf@jidanni.org \
--to=jidanni@jidanni$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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