git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Millisecond precision in timestamps?

From
Jeff King <peff@peff.net>
Date
Nov 28, 2012, 04:07 UTC
Message-ID
<20121128040739.GA4115@sigill.intra.peff.net>
In-Reply-To
<20121128034700.GD1669@thyrsus.com>
On Tue, Nov 27, 2012 at 10:47:00PM -0500, Eric S. Raymond wrote:
Show 13 quoted lines
> Jeff King <peff@peff.net>:
> > A much more compelling argument to me would be that you are doing some
> > bidirectional magic between git and svn, and you want to make make sure
> > that an svn->git->svn translation will result in the exact same bytes.
> > Then the argument is still "because SVN has it", but at least it is "and
> > we interoperate with it" and not simply chasing a cool but useless
> > feature.
> 
> Er, well, that *is* in fact the exact reason I want it.
> 
> I didn't put it exactly that way because I didn't expect anyone here
> to particularly care about round-tripping like that.  But remember 
> that I do a lot of stuff with repo surgery and conversion tools.

If that's what we really care about, then that opens up the possibilities for how we store the data. An extension header in the object might be convenient, but it opens up a lot of questions about what git will do with such a header (e.g., would it be part of git-log output?).

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.
Previous: Eric S. RaymondNext: Eric S. Raymond
Message 17 of 41 in “Millisecond precision in timestamps?”
  1. Eric S. RaymondNov 27, 2012
  2. Shawn PearceNov 27, 2012
  3. Junio C HamanoNov 27, 2012
  4. Eric S. RaymondNov 27, 2012
  5. Shawn PearceNov 27, 2012
  6. Eric S. RaymondNov 28, 2012
  7. David LangNov 28, 2012
  8. Felipe ContrerasNov 28, 2012
  9. Shawn PearceNov 28, 2012
  10. Jeff KingNov 28, 2012
  11. Jason PyeronNov 28, 2012
  12. Felipe ContrerasNov 28, 2012
  13. Eric S. RaymondNov 28, 2012
  14. Jeff KingNov 28, 2012
  15. Felipe ContrerasNov 28, 2012
  16. Eric S. RaymondNov 28, 2012
  17. Jeff KingNov 28, 2012
  18. Eric S. RaymondNov 28, 2012
  19. Junio C HamanoNov 28, 2012
  20. Eric S. RaymondNov 28, 2012
  21. David AguilarNov 28, 2012
  22. Andreas EricssonNov 28, 2012
  23. Robin RosenbergDec 5, 2012
  24. James CloosDec 10, 2012
  25. Thomas BergNov 28, 2012
  26. Felipe ContrerasNov 28, 2012
  27. Thomas BergNov 28, 2012
  28. Junio C HamanoNov 28, 2012
  29. Andreas EricssonNov 28, 2012
  30. Phil HordNov 29, 2012
  31. Jeff KingNov 29, 2012
  32. Eric S. RaymondNov 28, 2012
  33. Felipe ContrerasNov 28, 2012
  34. Junio C HamanoNov 28, 2012
  35. Pyeron, Jason J CTR (US)Nov 27, 2012
  36. Eric S. RaymondNov 29, 2012
  37. Junio C HamanoNov 29, 2012
  38. Felipe ContrerasNov 29, 2012
  39. Eric S. RaymondNov 29, 2012
  40. Junio C HamanoNov 29, 2012
  41. Eric S. RaymondNov 29, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.