Hello Everybody. I'm wondering about the proper process of contributing code. E.g. I have a small patch that would address a small memory leak (an end of session memory leak, so it is rather inconsequential). The problem is easy to spot, the fix is just two lines of code, all IMO very obvious. So should I first report a bug in bugzilla or just send a diff to this list? I'm sorry if the question is answered in a FAQ, I did check if the process is described somewhere but could not find it. I saw mails with old similar patches, but can't figure out what led to them, e.g. https://marc.info/?l=openssh-unix-dev&m=148378979902891&w=2 Markus
On Thu 2018-11-29 15:15:41 +0100, Markus wrote:> So should I first report a bug in bugzilla or just send a diff > to this list?Why not both? if you've already got an account in bugzilla, open a report there, and attach your patch. then send a short note to the list with a brief explanation and a pointer to the bugzilla ticket (and go ahead and include the patch in the e-mail, if it's a modest size). if you can only do one of those things, that's fine too -- but please do at least one! thanks for helping out with OpenSSH! --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20181129/4726ec75/attachment.asc>