On Tue, Nov 27, 2012 at 10:47:00PM -0500, Eric S. Raymond wrote:
> Jeff King <peff@xxxxxxxx>:
> > 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html