baz-import does not record Arch merges

[Aaron Bentley]

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

John Arbash Meinel wrote:
| I thought you had that working, which was why I was surprised to see
| that it didn't.
| Do you have an estimate when these will be brought into your mainline
| bzrtools?

A week or so is my guess.

| Yeah, I'm not sure what would be good. Colon makes for an awfully nice
| namespace separator.
| We could go the Mac route, and encode ":" as a "/" (mac does the
| opposite, encoding / as a :), effectively pushing the revisions into
| their own directories. :)
|
| We could do "Arch-"
| And just live with that.
| Or do all caps, with a space
| 'ARCH '

What's particularly ughly is that the null revision's name already has a
colon.  Now, the whole point of the null revision is that it doesn't
exist and can't be accessed, but it still is worrisome.

|>Martin's been reluctant to encode the IDs, but the only forbidden
|>characters so far were '/' and maybe '\'.
|
|
| I thought newline was forbidden. If it wasn't, we probably should make
| it be.

It's not, but that wouldn't be a bad idea.

I know for file-ids we are being more generous, and allowing
| spaces, etc, because Arch would use them.

Well, it's pretty much the same for file-ids and revision-ids.

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

iD8DBQFDdOV40F+nu1YWqI0RAvu0AJ44QOvkqxfzCMX4glkvAB0rKby/eQCeIHql
ic46rb0jDKuBrW4w7dg4STI=
=ldgC
-----END PGP SIGNATURE-----