[PATCH 1 of 2] tests: unify test-patchbomb
Mads Kiilerich
mads at kiilerich.com
Mon Aug 16 15:20:46 CDT 2010
Martin Geisler wrote, On 08/16/2010 08:51 PM:
> Even though you mailed the patch using the patchbomb extension, I could
> not apply it directly. The problem was the hunk that deleted the old
> patchbomb.out file, which had a "ö" encoded in both UTF-8 and Latin-1.
>
> I'm not sure, but I guess the mail ought to have been quoted-printable
> encoded or something like that. Instead it just had:
>
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 8bit
I don't think any mail headers could have made that work reliable and
rfc-compliant.
Mercurial is binary safe and doesn't care about encodings, but other
systems - such as mail systems and consoles - cares about encodings and
are not binary safe. It would solve some problems if we had a mode where
everything that isn't 7-bit or has inconsistent line endings or has
other control characters is encoded as git binary diffs (for a lack of a
better format).
http://mercurial.selenic.com/bts/issue2290 discusses similar issues.
/Mads
More information about the Mercurial-devel
mailing list