From: Geert Bosch <bosch@adacore.com>
To: tony.luck@intel.com
Cc: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>, git@vger.kernel.org
Subject: Re: mod-times (was: keyword expansion)
Date: Mon, 25 Apr 2005 14:13:43 -0400 [thread overview]
Message-ID: <3741014dfd79fce50999dc19d7029c40@adacore.com> (raw)
In-Reply-To: <200504251756.j3PHuSh01362@unix-os.sc.intel.com>
On Apr 25, 2005, at 13:56, tony.luck@intel.com wrote:
>> - Time stamp of the last modification of a file
>
> One way to do this would be to rip on some of the core fundamentals of
> GIT
> and store the time that an object was created inside the object. E.g.
>
> blob size secs-since-1970 ...
>
> Then "read-tree" could fill this into the cache, and checkout-cache
> could
> set the mod-time on the file when it creates it, which would mean that
> you
> could see the timestamp for a file simply by using "ls -l file".
Of course this negates the idea of content-based storage, since you
want two copies of the same content with different time-stamps to share
the same blob.
-Geert
next prev parent reply other threads:[~2005-04-25 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 0:23 keyword expansion Thomas Glanzmann
2005-04-25 17:56 ` mod-times (was: keyword expansion) tony.luck
2005-04-25 18:10 ` Thomas Glanzmann
2005-04-25 18:13 ` Geert Bosch [this message]
2005-04-26 0:34 ` Linus Torvalds
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=3741014dfd79fce50999dc19d7029c40@adacore.com \
--to=bosch@adacore.com \
--cc=git@vger.kernel.org \
--cc=sithglan@stud.uni-erlangen.de \
--cc=tony.luck@intel.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 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).