Looking at jcheck
hg.openjdk.java.net/code-tools/jcheck/file/tip/jcheck.py
I suspect this will pretty much disable the check of the initial lines that
look like
[0-9]+: .*
in other words, these lines can look like any number followed by ":" and any
text.
But I'm not a Python expert.
So this looks ok to me, with the understanding that these bugids now only refer
to your special
JIRA instance.
-kto
On Feb 21, 2013, at 10:07 AM, Omair Majid wrote:
> Hi,
>
> I would like to have everyone be able to push commits into the openjdk6
> repository without needing access to a non-public bug tracker.
> Currently, jcheck enforces that a commit message includes a bug id. The
> following webrev configures jcheck to allow commits with bug ids that do
> not match the bug ids that the Oracle-internal JIRA instance produces:
>
> http://cr.openjdk.java.net/~omajid/webrevs/relax-jdk6-bugids/00/
>
> It should be completely fine to push a commit with a bug id from
> Oracle-internal JIRA instance, though.
>
> Any thoughts, concerns or objections?
>
> I will need a bug id from JIRA to push this, but this will probably be
> the last commit that needs one.
>
> Thanks,
> Omair
>
> --
> PGP Key: 66484681 (http://pgp.mit.edu/)
> Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681
