To add some context, the problem here is that when I squashed METRON-799 it
became 3 commits, in order to keep proper attribution. I missed having the
jira on the last of the 3 commits during the squash. The other two commits
do still have it:
commit 41b5b1050cf29e5dcb5d0c36b5a9dbd1cafa745e
The MPack should function in a kerberized cluster (justinleet) closes
apache/incubator-metron#518
commit 55062fb79a85722c909906874e0772f51b18953d
METRON-799 The MPack should function in a kerberized cluster (dlyle via
justinleet) closes apache/incubator-metron#518
commit 187ef373a6cc0f89696349acc35ddeddbfd836ef
METRON-799 The MPack should function in a kerberized cluster
(justinleet) closes apache/incubator-metron#518
On Sun, Apr 30, 2017 at 8:03 PM, [email protected] <[email protected]> wrote:
> It looks like METRON-799 <https://issues.apache.org/jira/browse/METRON-799
> >
> (#518 <https://github.com/apache/incubator-metron/pull/518>) got commit
> <https://github.com/apache/incubator-metron/commit/
> 41b5b1050cf29e5dcb5d0c36b5a9dbd1cafa745e>
> without having the JIRA in the title. Is this enough of a concern
> to reword the commit message? I know there have been some concerns with
> changing ever changing history, no matter how small, but I figured I would
> bring it up to discuss. Thanks,
>
> Jon
> --
>
> Jon
>
