<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 3, 2014 at 10:03 PM, Shawn Wells <span dir="ltr"><<a href="mailto:shawn@redhat.com" target="_blank">shawn@redhat.com</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"><div><div class="h5">
<div>On 9/3/14, 10:02 AM, Gabe Alford wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail_extra">
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Speaking
about blockers (issues that definitely need to go into next
release)<br>
would it be possible to set up an agreement that such fixes
would receive the<br>
[BLOCKER] prefix together with the [PATCH] prefix?<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Are you talking about adding a "Blocker"
label to the pull request? Or when you `git commit` adding
"[Blocker]" to your commit msg before you initiate a pull
request?</div>
</blockquote>
<br></div></div>
Label in the repo that we could query against, ideally.<br></div></blockquote><div><br></div><div>Would `git log` or `git shortlog` work for this? It could easily be scripted with either of those.<br></div></div><br>
</div></div>