From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jeff King <peff@peff.net>
Cc: Shawn Pearce <spearce@spearce.org>,
Felipe Contreras <felipe.contreras@gmail.com>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: Millisecond precision in timestamps?
Date: Tue, 27 Nov 2012 23:25:30 -0500 [thread overview]
Message-ID: <20121128042529.GA3864@thyrsus.com> (raw)
In-Reply-To: <20121128040739.GA4115@sigill.intra.peff.net>
Jeff King <peff@peff.net>:
> Felipe suggested using git-notes to add the metadata, which I think is a
> reasonable first step. The git side of the code is already written, and
> the concept is nicely modularized away from the core of git. Nobody has
> to care about it but your importer, and anybody who wants to query it[1]
> can do so by requesting the note.
>
> -Peff
>
> [1] And you do not have to limit yourself to timestamps, if there is
> other metadata about each commit you end up wanting to store for a
> clean bi-directional conversion.
I have actually wanted something like this quite badly. Not so much
for timestamps (though that would be nice), but it would be useful if
each commit could carry a fossil-ID attribute that points at the
Subversion commit it was derived from.
I've tried to make notes work for this, but couldn't beat it into
doing what I was after. Shawn, is there a way that the import stream
syntax can declare a note with in-line data attached to the commit where
it's declared?
I tried just using the mark of the current commit, but git throws an error
because it thinks that mark is not yet declared when the note fileop
is parsed.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2012-11-28 4:25 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 [this message]
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
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=20121128042529.GA3864@thyrsus.com \
--to=esr@thyrsus.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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 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).