Junio C Hamano <gits...@pobox.com>:
> That is exactly why I said it is all relative. If it helps your
> application, you can weigh the pros-and-cons yourself and choose to
> throw "junk" extended header fields in the commit objects you
> create, using hash-object (or commit-tree). You can read it out
> using cat-file and do whatever you want to do with it, and modern
> Git (v1.5.0 was from early 2007) and tools that are designed to work
> with Git know to ignore such "junk" field.
A good start. But remember that reposurgeon's entire interface to the
git object level is through fast-export/fast-import. I need import-
stream syntax for these.
bzr's syntax would do:
-------------------------------------------
mark :1
committer Eric S. Raymond <e...@thyrsus.com> 1289147634 -0500
data 14
First commit.
property branch-nick 12 bzr-testrepo
M 644 inline README
data 41
This is a test file in a dummy bzr repo.
-------------------------------------------
If we actually care about keys being full utf-8 with embedded whitespace
it should look more like this:
-------------------------------------------
mark :1
committer Eric S. Raymond <e...@thyrsus.com> 1289147634 -0500
data 14
First commit.
property 11
branch-nick
propval 12
bzr-testrepo
M 644 inline README
data 41
This is a test file in a dummy bzr repo.
-------------------------------------------
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
