[darcs-users] machine-readable formats

Reinier Lamers tux_rocker at reinier.de
Sat Sep 4 17:11:15 UTC 2010


On Friday September 03 2010 12:35 Petr Rockai wrote:
> For changes, the metadata could be probably escaped like it is in the
> terminal output (those <U+NNNN> bits), just using YAML escapes. I think
> with Reinier's changes, we do a reasonable job of letting valid UTF-8
> through, while catching any non-UTF garbage.

And Lele Gaifax said:
> Unfortunately, the hard and most annoying aspect was to
> workaround imprecise non-ASCII chars encoding, and from fast memory it
> is still the only occasional glitch in the code, that needed some
> tweaks now and then.

I've been thinking of redoing our machine-readable output generation for a fix 
of the encoding-related issue1143.

The patch metadata serves two purposes:
  * Explaining what the patch does to humans
  * Identifying the patch to machines

For the first purpose, we need a text (Unicode) representation. For the 
second, we are tied to a binary representation by backwards compatibility.

Perhaps we have to include both representations in our machine readable 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.osuosl.org/pipermail/darcs-users/attachments/20100904/2d59e8b0/attachment.pgp>

More information about the darcs-users mailing list