indicating type(level?) of message

[Martin Geisler]

timeless <timeless at gmail.com> writes:

> FUJIWARA wrote:
>> But indicating type of message(e.g: ERROR, WARNING, and so on) is more
>> friendly for novice ones, isn't it ?
>
> personally, I agree.

I would also like to see our info, warning, and error messages
standardized. But we must be careful not to change the output too much:

  http://mercurial.selenic.com/wiki/CompatibilityRules

> The other point of reference I'd make is that Solaris messages include
> IDs which people can use to look up additional information. If a
> message said
> "files over 10MB may cause memory and performance problems"
>
> it could include an identifier (which for mercurial would probably
> lead to a wiki page) that can further describe the costs, point to
> relevant bugs on the topic, and provide alternative suggestions.

Is it not enough that people can search for the error online? I fear
that maintaining such identifiers will be an administrative burden and
it's not something I've seen other projects to.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090710/7fd5219f/attachment.pgp