Re: author_transforms with Mercurial
Greg Ward <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Aug 4, 2009 at 4:46 PM, Michael > But please note that author_transforms as implemented for cvs2svn > (recently implemented) does *not* enforce the "name <email>" form. Why > don't you just base your code on that? Ahh! Excellent suggestion. I had not noticed that before. BTW, the comment in cvs2svn-example.options is a bit inaccurate: > All values should be either 16-bit strings > # (i.e., with "u" as a prefix) They're "Unicode strings", not "16-bit strings". That's how Python consistently refers to them, with good reason. (If you want to get really picky, I believe Unicode is a 21-bit character set.) > I am not crazy about having behavior implicitly depend on parameter > types, especially as the options files are likely to be edited by people > who don't know Python. And the tuple version is actually a bit *more* > typing than the string version. I would prefer to live with the string > version for cvs2hg, unless you think it would be a hardship. Strings are good. I like strings. Strings it shall be. Greg ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2380823 To unsubscribe from this discussion, e-mail: [[email protected]].