<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 04/20/2016 11:35 AM, Martin Malina
      wrote:<br>
    </div>
    <blockquote
      cite="mid:2D282B6F-7E76-4DCB-98E5-66F7882D4FAD@redhat.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br class="">
      <div class=""><br class="">
      </div>
      <div class="">You see, there is nothing different - apart from
        checksums, it's the bundle version. But that is outside of the
        changes - that is just there for context, not part of the
        commits. Any idea why the patch-id is different?</div>
    </blockquote>
    <br>
    The patch-id includes context. It ignores whitespace. So yeah,
    different context will lead to a false-positive. There's no really
    efficient way to get rid of these without writing your own utility i
    guess ;) <br>
    <br>
    <blockquote
      cite="mid:2D282B6F-7E76-4DCB-98E5-66F7882D4FAD@redhat.com"
      type="cite">
      <div class=""><br class="">
      </div>
      <div class="">-Martin</div>
      <div class="">
        <br class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">On 18. 4. 2016, at 23:09, Rob Stryker &lt;<a
                moz-do-not-send="true"
                href="mailto:rob.stryker@redhat.com" class=""><a class="moz-txt-link-abbreviated" href="mailto:rob.stryker@redhat.com">rob.stryker@redhat.com</a></a>&gt;
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <meta content="text/html; charset=windows-1252"
                http-equiv="Content-Type" class="">
              <div text="#000000" bgcolor="#FFFFFF" class="">
                <div class="moz-cite-prefix">On 04/18/2016 05:05 AM, Max
                  Rydahl Andersen wrote:<br class="">
                </div>
                <blockquote
                  cite="mid:4A70E7DC-6C51-45CC-B54B-9177FAC346E3@redhat.com"
                  type="cite" class=""><br class="">
                  great initiative - may I suggest you do a PR for your
                  script and put it at <a moz-do-not-send="true"
                    class="moz-txt-link-freetext"
href="https://github.com/jbosstools/jbosstools-build-ci/tree/jbosstools-4.3.x/util">https://github.com/jbosstools/jbosstools-build-ci/tree/jbosstools-4.3.x/util</a>
                  where we have other such utilities. <br class="">
                  <br class="">
                  Also, might be easier if you put the run info into 
                  jira since the output is quite hard to read/use here
                  from mail. <br class="">
                  <br class="">
                  btw. it looks like this tool actually is very good at
                  finding the false positives - i.e. change in pom.xml
                  where it just changes version seem to be something you
                  could filter out somehow ? <br class="">
                  <br class="">
                </blockquote>
                <br class="">
                <br class="">
                First, I disagree that these are false-positives ;)  
                These are commits that are in maintenance that aren't in
                master.  <br class="">
                <br class="">
                And, in all honesty, I think it'd be a mistake to simply
                filter them out. I think it's much better to list the
                false positive and let the component owner use his
                judgment whether the patch needs further inspection or
                not. Such simple version-changes will be very very easy
                for a human to spot as irrelevant to master.  This may
                cause the repository owner to waste 2-3 seconds for each
                commit, but it guarantees that every possible unmatched
                commit is found. <br class="">
                <br class="">
                I think this is much better and safer than possibly
                adding some logic to filter out version changes and
                later discover that the logic was wrong and so it was
                hiding legitimately missing commits from being shown. 
                Also, since we're not inspecting the patches at all, but
                rather comparing patch-id's, it would make the script
                much much more complicated. <br class="">
                <br class="">
                <i class="">Il meglio č nemico del bene  -  Perfect is
                  the enemy of good<br class="">
                  <br class="">
                </i><a moz-do-not-send="true"
                  class="moz-txt-link-freetext"
                  href="https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good">https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good</a><br
                  class="">
                <i class=""><br class="">
                </i><br class="">
                <br class="">
              </div>
              _______________________________________________<br
                class="">
              jbosstools-dev mailing list<br class="">
              <a moz-do-not-send="true"
                href="mailto:jbosstools-dev@lists.jboss.org" class="">jbosstools-dev@lists.jboss.org</a><br
                class="">
              <a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></div>
          </blockquote>
        </div>
        <br class="">
      </div>
    </blockquote>
    <br>
  </body>
</html>