From: Jakub Narebski <jnareb@gmail.com>
To: Tong Sun <suntong001@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git check out file time
Date: Sat, 07 Aug 2010 06:46:20 -0700 (PDT) [thread overview]
Message-ID: <m3aaoyo7sz.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTinuD8YQ+maWwD3v1C0B4YCOdTS4OsVjHLizga3c@mail.gmail.com>
Tong Sun <suntong001@gmail.com> writes:
> Quick Q, is it possible to keep the original file time from the git
> server when checking out / cloning a local repo?
>
> When I did
>
> git clone git://git.remote...
>
> All my local git files are set to the check out time.
>
> Please help and CC me when replying.
Only with third-party extra tools such as Metastore (or etckeeper that
uses it), or git-cache-meta (or IsiSetup), see
https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools
Git itself doesn't store original file time, and with its intended use
it would screw up mtime-based make rebuilding.
HTH
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2010-08-07 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 4:54 git check out file time Tong Sun
2010-08-07 13:46 ` Jakub Narebski [this message]
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=m3aaoyo7sz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=suntong001@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 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).