From: "Eric S. Raymond" <esr@thyrsus.com>
To: Steven Michalske <smichalske@gmail.com>
Cc: Thomas Berg <merlin66b@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Shawn Pearce <spearce@spearce.org>, git <git@vger.kernel.org>
Subject: Re: Millisecond precision in timestamps?
Date: Thu, 29 Nov 2012 01:16:50 -0500 [thread overview]
Message-ID: <20121129061650.GB25537@thyrsus.com> (raw)
In-Reply-To: <E4C993F4-B7A4-4CB6-A9EA-BFE98BE3A381@gmail.com>
Steven Michalske <smichalske@gmail.com>:
> Would having arbitrary key value pairs be useful in the git data
> model? We could have ones that affect the sha1 and others that are
> transparent.
My tools would have several uses for these.
bzr's implementation of import streams has a commit-propperties extension.
reposurgeon can read, display.. and manipulate these key/value pairs.
I do wish they were in core git.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2012-11-29 6:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 20:48 Millisecond precision in timestamps? Eric S. Raymond
2012-11-27 21:41 ` Shawn Pearce
2012-11-27 22:06 ` Junio C Hamano
2012-11-27 23:04 ` Eric S. Raymond
2012-11-27 23:49 ` Shawn Pearce
2012-11-28 0:12 ` Eric S. Raymond
2012-11-28 0:22 ` David Lang
2012-11-28 0:26 ` Felipe Contreras
2012-11-28 1:07 ` Shawn Pearce
2012-11-28 1:17 ` Jeff King
2012-11-28 1:29 ` Jason Pyeron
2012-11-28 1:42 ` Felipe Contreras
2012-11-28 3:23 ` Eric S. Raymond
2012-11-28 3:30 ` Jeff King
2012-11-28 3:44 ` Felipe Contreras
2012-11-28 3:47 ` Eric S. Raymond
2012-11-28 4:07 ` Jeff King
2012-11-28 4:25 ` Eric S. Raymond
2012-11-28 7:29 ` Junio C Hamano
2012-11-28 7:58 ` Eric S. Raymond
2012-11-28 8:04 ` David Aguilar
2012-11-28 10:14 ` Andreas Ericsson
2012-12-05 23:37 ` Robin Rosenberg
2012-12-10 20:56 ` James Cloos
2012-11-28 8:19 ` Thomas Berg
2012-11-28 8:44 ` Felipe Contreras
2012-11-28 9:10 ` Thomas Berg
[not found] ` <E4C993F4-B7A4-4CB6-A9EA-BFE98BE3A381@gmail.com>
2012-11-29 6:16 ` Eric S. Raymond [this message]
2012-11-29 7:11 ` Junio C Hamano
2012-11-29 7:22 ` Felipe Contreras
2012-11-29 10:38 ` Eric S. Raymond
2012-11-29 16:42 ` Junio C Hamano
2012-11-29 19:02 ` Eric S. Raymond
2012-11-28 17:57 ` Junio C Hamano
2012-11-28 10:10 ` Andreas Ericsson
2012-11-29 19:14 ` Phil Hord
2012-11-29 20:01 ` Jeff King
2012-11-28 1:11 ` Eric S. Raymond
2012-11-28 1:36 ` Felipe Contreras
2012-11-28 2:01 ` Junio C Hamano
2012-11-27 21:44 ` Pyeron, Jason J CTR (US)
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=20121129061650.GB25537@thyrsus.com \
--to=esr@thyrsus.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=merlin66b@gmail.com \
--cc=peff@peff.net \
--cc=smichalske@gmail.com \
--cc=spearce@spearce.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.