Re: [PATCH resend] Do not create commits whose message contains NUL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 14, 2011 at 02:23:29PM +0900, Miles Bader wrote:

> Jeff King <peff@xxxxxxxx> writes:
> >      But maybe it would be nicer to say something like:
> >
> >        error: your commit message contains NUL characters.
> >        hint: This is often caused by using multibyte encodings such as
> >        hint: UTF-16. Please check your editor settings.
> 
> I think the error message with the hint is much better for users, but
> isn't the term "multibyte" a little misleading here?  It seems like
> it's really _wide_ encodings that are generally the culprit.

Yeah, wide is probably a better term. I'm not sure it is rigorously
defined anywhere, but in general I think it refers to the set of
encodings that do not care about the embedding of 8-bit ascii bytes as
subsets.

-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]