<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">Le 15/10/2014 11:56, Christopher Yeoh a
      écrit :<br>
    </div>
    <blockquote
cite="mid:CANCY3ecFYwsS9PM5UsXSyEdTDuBoj1XqGCweQrm7JENT3hseOQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, Oct 15, 2014 at 7:31 PM, Alex
            Xu <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:xuhj@linux.vnet.ibm.com" target="_blank">xuhj@linux.vnet.ibm.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="HOEnZb">
                <div class="h5">On 2014年10月15日 14:20, Christopher Yeoh
                  wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    Hi,<br>
                    <br>
                    I was wondering what people thought of having a
                    convention of adding<br>
                    an APIImpact flag to proposed nova specs commit
                    messages where the<br>
                    Nova API will change? It would make it much easier
                    to find proposed<br>
                    specs which affect the API as its not always clear
                    from the gerrit<br>
                    summary listing.<br>
                  </blockquote>
                </div>
              </div>
              +1, and is there any tool can be used by search flag?<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
              </blockquote>
            </blockquote>
            <div><br>
            </div>
            <div>Can use the message: filter in the gerrit web search
              interface to search in commit messages, or</div>
            <div>alternatively use gerritlib to write something custom.</div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    IMHO, asking people to put a tag on a commit msg is good but
    errorprone because there could be some misses.<br>
    Considering that API changes require new templates, why not asking
    for people to provide on a separate tpl file the changes they want
    to provide, and make use of the Gerrit file pattern search like<br>
    specs/kilo/approved/*.tpl ?<br>
    <br>
    <br>
    -Sylvain<br>
    <br>
    <br>
    <blockquote
cite="mid:CANCY3ecFYwsS9PM5UsXSyEdTDuBoj1XqGCweQrm7JENT3hseOQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>Regards,</div>
            <div><br>
            </div>
            <div>Chris </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>