commit performance regression in 0.11

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:

> Well all of these start exposing "implementation details", right?

Sure.

> Also, what do people think about trying to get my no-hash-prefix version
> of the repository into 0.12? I haven't been pushing for it, because we
> haven't tested it a whole lot. But it really is a lot faster for a new
> kernel-sized add + commit (like 1/2 the time). Since your Knit2 format
> is experimental, I think we could just put it in the same format, and
> then we don't have the overhead of 2 format changes.

I think it would be best to bump to Knit3, and just drop support for the
current Knit2.  There's always the chance of confusion if we retain the
same format string.

> Another possibility would be to make the hash-prefix configurable with
> another control file. So people could decide which one they wanted to
> use, in case a given filesystem performed poorly.

I'd tend to go YAGNI on that.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFGDih0F+nu1YWqI0RAp3PAJ4kHAQbnH/DNddtJvorYW6Sw6WWXwCfb3aj
zO9Qn6kezG1p/bT+q7Unyk0=
=0A2H
-----END PGP SIGNATURE-----