Hi, On 19/12/14 08:12, Daniel Kahn Gillmor wrote: > Presumably that means that they're forwarded from somewhere, but i don't > know where. where are they forwarded from? For some strange reason, I sent many of the reports to ow...@bugs.debian.org instead of the correct report email, so I just forwarded them to the correct email.
> Many of the patches suggest familiarity with C, which is great. Do you > know how to generate patches in the unified diff format? Including a > machine-appliable patch with each report would make it easier for people > to see the changes you're proposing. Yes, I know how to use `diff', but what do you mean by machine-appliable? I usually just use `diff -Naur'. > Also: were you using a tool to find these problems, or just reading the > code yourself? If you're using a tool to find them, what tool? Using a combination of 'Coverity', and manually looking. > Finally, most of these look like they might be issues in the upstream > code. This kind of report is likely to be most useful submitted > directly to the upstream development team at <gnupg-de...@gnupg.org>. > > I can do all the patch generation and forwarding to upstream if you > like, but it sounds like you could be even more helpful interacting with > upstream directly. If you're interested in figuring out how to do that, > but aren't sure where to start, i'd be happy to help you sort it out. Yes, probably, I should have, but I looked at the bug report page and it seems that the develoeprs are inactive. I didn't really have a good look though, so I may have missed other activity. Anyways, if you could do the patch generation and fowarding, that would be great. I really can't be bothered doing it myself, to be honest, lol. They're all mostly one-liner fixes. Thanks, -- -- Joshua Rogers <https://internot.info/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
