From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'Hector Santos'" <winserver.support@winserver.com>,
<git@vger.kernel.org>
Subject: RE: Git "Keeping Original Dates"
Date: Mon, 5 Jun 2017 17:25:48 -0400 [thread overview]
Message-ID: <1C2B896999CB4549BCAC61EB369E932E@blackfat> (raw)
In-Reply-To: <5935C999.5060801@winserver.com>
> -----Original Message-----
> From: Hector Santos
> Sent: Monday, June 5, 2017 5:14 PM
>
> I'm implementing GIT. If there an option or compile/version that "keep"
file timestamps?
That is not in the tree data structure, see below.
root@blackfat /projects/tipsoftheday
$ git cat-file -p head
tree 4ca3c2a853c8e817d7de8563c331899cace8ee85
parent 2a33f293df6df0d3978612e41fb1ecd52e2450a5
author Jason Pyeron <jpyeron@pdinc.us> 1496424815 -0400
committer Jason Pyeron <jpyeron@pdinc.us> 1496424815 -0400
add JDK to CM
root@blackfat /projects/tipsoftheday
$ git cat-file -p 4ca3c2a853c8e817d7de8563c331899cace8ee85
040000 tree 76094b81b3877b5b27cd4fe518fa0708af3cefed admin
040000 tree c66a88871c285e1485f92be0f8fa47185d94d0b3 client
040000 tree 460495af209a580e65b5d0b38132d774ddb283b7 database
040000 tree 264b191b036180039f3fd8c5d56c2b6800cb2ca2 doc
040000 tree dd128195971f7bafa56371aa6027d7c6bc80f351 middleware
040000 tree 7861fd39923950d501d4e39aeac4762f7daaca6b reports
040000 tree 2ad3dedf0313ae775321c88c53741a4b4a7e87b0 tools
I wish it was an allowable extension, the date could be between the mode and
object type.
v/r,
Jason Pyeron
next prev parent reply other threads:[~2017-06-05 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 21:14 Git "Keeping Original Dates" Hector Santos
2017-06-05 21:25 ` Jason Pyeron [this message]
2017-06-05 22:06 ` Ævar Arnfjörð Bjarmason
2017-06-05 23:36 ` Hector Santos
2017-06-06 16:09 ` Theodore Ts'o
2017-06-05 21:27 ` Ævar Arnfjörð Bjarmason
2017-06-06 1:22 ` Jeff King
2017-06-06 2:43 ` Hector Santos
2017-06-06 7:12 ` Konstantin Khomoutov
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=1C2B896999CB4549BCAC61EB369E932E@blackfat \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=winserver.support@winserver.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