From: Hector Santos <winserver.support@winserver.com>
To: "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git "Keeping Original Dates"
Date: Mon, 05 Jun 2017 22:43:47 -0400 [thread overview]
Message-ID: <593616E3.6050903@winserver.com> (raw)
In-Reply-To: <20170606012159.yqypreouvmmrfifd@sigill.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On 6/5/2017 9:22 PM, Jeff King wrote:
> There are existing scripts which implement this approach, like
> metastore:
>
> https://github.com/przemoc/metastore
>
> I haven't used it, but I think it's fairly mature, as it has been around
> since the early days of Git.
>
> -Peff
>
I wasn't considering other "metadata" other than time stamps, but I
suppose the metadata would include the time stamps, file attributes
and possibly "alternate file streams" as well?
Thanks anyway, I will explore it.
--
Hector, Engineering & Technical Support
Santronics Software, Inc.
http://www.santronics.com (sales)
http://www.winserver.com (support)
http://www.winserver.com/AupInfo (Online AUP Help)
Office: 305-248-3204
[-- Attachment #2: winserver_support.vcf --]
[-- Type: text/x-vcard, Size: 145 bytes --]
begin:vcard
fn:Hector Santos
n:Santos;Hector
email;internet:winserver.support@winserver.com
tel;work:305-248-3204
version:2.1
end:vcard
next prev parent reply other threads:[~2017-06-06 2:43 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
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=593616E3.6050903@winserver.com \
--to=winserver.support@winserver.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).