<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/23/2014 03:02 PM, Joe Gordon
wrote:<br>
</div>
<blockquote
cite="mid:CAHXdxOf-i70Vxr6WZXpaGdW2+AtzjjHRGLj4QXf9FMg_CdJRsg@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sat, May 24, 2014 at 2:23 AM,
Nachi Ueno <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:nachi@ntti3.com" target="_blank">nachi@ntti3.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks<br>
<br>
I believed we should link bug or bp for any commit except
automated<br>
commit by infra.<br>
However, I found also there is no written policy for this.<br>
so may be, I'm wrong for here.<br>
<br>
The reason, we need bug or bp linked , is<br>
<br>
(1) Triage for core reviewing </blockquote>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
(2) Avoid duplication of works<br>
</blockquote>
<div><br>
</div>
<div>I'm not sure how this will help. folks will just file
duplicate bugs write before the push there patch for
review.</div>
<div> </div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
When you start to file a bug on Launchpad, it will first do a search
based on the summary you enter, then provide a list of existing bugs
with similar titles. It's not perfect, but I think this is what
Nachi was referring to.<br>
<br>
<br>
-Chris<br>
<br>
</body>
</html>