Mon, 25 Jan 2010 01:23:34 -0600 check-code: check thyself
Matt Mackall <mpm@selenic.com> [Mon, 25 Jan 2010 01:23:34 -0600] rev 10286
check-code: check thyself
Fri, 29 Jan 2010 01:04:38 +0100 Merge with stable.
Martin Geisler <mg@lazybytes.net> [Fri, 29 Jan 2010 01:04:38 +0100] rev 10285
Merge with stable.
Thu, 28 Jan 2010 11:27:09 +0000 patchbomb: document [patchbomb] config section for addresses stable
Christian Ebert <blacktrash@gmx.net> [Thu, 28 Jan 2010 11:27:09 +0000] rev 10284
patchbomb: document [patchbomb] config section for addresses
Thu, 28 Jan 2010 10:38:29 +0000 hgrc.5: whether bcc is prompted for is up to the extension stable
Christian Ebert <blacktrash@gmx.net> [Thu, 28 Jan 2010 10:38:29 +0000] rev 10283
hgrc.5: whether bcc is prompted for is up to the extension There is no code in mail.py that forbids an extension to prompt for bcc.
Mon, 25 Jan 2010 00:05:27 -0600 many, many trivial check-code fixups
Matt Mackall <mpm@selenic.com> [Mon, 25 Jan 2010 00:05:27 -0600] rev 10282
many, many trivial check-code fixups
Mon, 25 Jan 2010 00:05:22 -0600 Introduce check-code.py
Matt Mackall <mpm@selenic.com> [Mon, 25 Jan 2010 00:05:22 -0600] rev 10281
Introduce check-code.py check-code is a simple regex-based framework for checking our code and tests for common style and portability errors. Currently, it knows a fair amount about our Python and C style, and a little about common shell script portability problems.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -6 +6 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip