<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 07/02/2013 12:59, Paul Menzel wrote:<br>
</div>
<blockquote cite="mid:1360238353.5796.67.camel@mattotaupa"
type="cite">
<pre wrap="">Dear SANE folks,
yesterday I created several new tickets and attached patches to some of
them, like [1].
[#314016] Cppcheck: [backend/hp-device.c:351,430]: (error) Possible null pointer dereference
Looking at the Git history it looks like though that for example the
last commit was submitted and discussed on this mailing list, sane-devel
[2].
commit 883d19145255ca098b89a9c2a5939c69034c98d8
Author: Rolf Bensch <a class="moz-txt-link-rfc2396E" href="mailto:roben-guest@alioth.debian.org"><roben-guest@alioth.debian.org></a>
Date: Wed Feb 6 22:16:58 2013 +0100
fixed button support for Canon Pixma MG6200
So to know what to do and what the current process is to get patches in,
should I bring the issues up to this list or should I just wait and
leave them in the Alioth tracker?
Thanks,
Paul
[1] <a class="moz-txt-link-freetext" href="https://alioth.debian.org/tracker/index.php?func=detail&aid=314016&group_id=30186&atid=410366">https://alioth.debian.org/tracker/index.php?func=detail&aid=314016&group_id=30186&atid=410366</a>
[2] <a class="moz-txt-link-freetext" href="http://lists.alioth.debian.org/pipermail/sane-devel/2013-February/thread.html">http://lists.alioth.debian.org/pipermail/sane-devel/2013-February/thread.html</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Hello,<br>
<br>
opening a bug and sending a mail, or sending only a mail are OK
for me. Opening a bug, may not be enough, specially if it is not
affected to anyone, or if it is too broad. The #313848 is a good
example, it spans other several backends, is not affected to anybody
and has this unattractive comment 'there may be some false
positives'. <br>
Since I have more things to do than time to do it, I'd rather
not dig into a big report to see if I have something to fix. And
when I (too rarely) look at the issue tracker, I prefer to look into
reports that have clear description.<br>
<br>
<br>
Regards,<br>
Stef<br>
<pre wrap="">
</pre>
</body>
</html>