Mercurial > hg
comparison hgext/color.py @ 25186:80c5b2666a96
extensions: document that `testedwith = 'internal'` is special
Extension authors (notably at companies using hg) have been
cargo-culting the `testedwith = 'internal'` bit from hg's own
extensions, which then defeats our "file bugs over here" logic in
dispatch. Let's be more aggressive about trying to give extension
authors a hint about what testedwith should say.
author | Augie Fackler <augie@google.com> |
---|---|
date | Tue, 28 Apr 2015 16:44:37 -0400 |
parents | 2f88821856eb |
children | ceec79b5657a |
comparison
equal
deleted
inserted
replaced
25185:bf6b476f3b36 | 25186:80c5b2666a96 |
---|---|
160 from mercurial import templater, error | 160 from mercurial import templater, error |
161 from mercurial.i18n import _ | 161 from mercurial.i18n import _ |
162 | 162 |
163 cmdtable = {} | 163 cmdtable = {} |
164 command = cmdutil.command(cmdtable) | 164 command = cmdutil.command(cmdtable) |
165 # Note for extension authors: ONLY specify testedwith = 'internal' for | |
166 # extensions which SHIP WITH MERCURIAL. Non-mainline extensions should | |
167 # be specifying the version(s) of Mercurial they are tested with, or | |
168 # leave the attribute unspecified. | |
165 testedwith = 'internal' | 169 testedwith = 'internal' |
166 | 170 |
167 # start and stop parameters for effects | 171 # start and stop parameters for effects |
168 _effects = {'none': 0, 'black': 30, 'red': 31, 'green': 32, 'yellow': 33, | 172 _effects = {'none': 0, 'black': 30, 'red': 31, 'green': 32, 'yellow': 33, |
169 'blue': 34, 'magenta': 35, 'cyan': 36, 'white': 37, 'bold': 1, | 173 'blue': 34, 'magenta': 35, 'cyan': 36, 'white': 37, 'bold': 1, |