Multiple whoami?

[John Arbash Meinel]

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


...

> We could make the "author" property multi-value using a "\n" separator
> or something that is unlikely to be in any existing revision properties,
> and then define that the result of "get_apparent_author" should be
> split on this character to get the list of authors.
> 
> That of course comes with a risk of breaking existing things. We could
> invent a new multi-value property, e.g. "other-authors" and put any
> overflow in there. Then we can add "get_apparent_authors" that knows
> what to do.

I would change 'author' to allow multiple fields with '\n' as the
separator. Then update 'get_apparent_author' to return one value but
deprecate it. And add 'get_apparent_authors()' which returns a list.

> 
> The other alternative as I see it is to have lots of author revision
> properties. We can have "author", "author2", "author3", etc. It's not
> very cute, but it avoids the need to reject a single character in the
> author string, and doesn't risk breaking existing users of the property.
> 
> We could have a "author-count" property as well that would save some
> "while author_num in revision.properties:" code, but adds duplication.
> 
> What's the best way for me to approach this?
> 
> Thanks,
> 
> James

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmmuOkACgkQJdeBCYSNAAPXzgCfURFi7bkQStj5/MX2Y6MGU1wR
8t8An1hS8DDb6lhQ8bmAZ4Dw3Q7x3xcQ
=l2r4
-----END PGP SIGNATURE-----