<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 29 February 2016 at 15:34, Hirofumi Ichihara <span dir="ltr"><<a href="mailto:ichihara.hirofumi@lab.ntt.co.jp" target="_blank">ichihara.hirofumi@lab.ntt.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Hi Armando,<br>
    <br>
    I didn't know and I have such patch now.<br>
    Thank you for your message.<br>
    <br>
    I have seen that neutron spec has the flag in the Commit Message.<br>
    In such case, we don't need to add the flag into the implementation
    patch, do we?<br></div></blockquote><div><br></div><div>I would not personally add a DocImpact on a spec patch.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    <br>
    Thanks,<br>
    Hirofumi<div><div class="h5"><br>
    <br>
    <div>On 2016/03/01 7:18, Armando M. wrote:<br>
    </div>
    </div></div><blockquote type="cite"><div><div class="h5">
      <div dir="ltr">Hi Neutrinos,
        <div><br>
        </div>
        <div>Please remember that what you decorate a commit message
          with DocImpact, this must be followed by a brief description
          of the documentation impact [1]. Also, please be aware that
          currently, as soon as the patch merges, a bug report is filed
          against the Launchpad project of the targeted repo. This is
          tagged with 'doc' and '<repo-name>' [2].</div>
        <div><br>
        </div>
        <div>So, if you have a train of patches affecting the same
          feature (client side, server side, *-aas projects etc), be
          mindful to where you put the tag and avoid adding DocImpact to
          more than one commit message, unless the documentation target
          is indeed meant to be separate.</div>
        <div><br>
        </div>
        <div>Cheers,</div>
        <div>Armando</div>
        <div><br>
        </div>
        <div>[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html</a></div>
        <div>[2] <a href="https://bugs.launchpad.net/neutron/+bugs?field.tag=doc" target="_blank">https://bugs.launchpad.net/neutron/+bugs?field.tag=doc</a></div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </div>

<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>