Date: Mon, 22 Jun 2020 21:46:30 -0700 From: Neel Chauhan <neel@neelc.org> To: Alexander Leidinger <Alexander@leidinger.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Getting patches reviewed as an outside contributor Message-ID: <fb71e5ec139be0178f11abb9eb15b305@neelc.org> In-Reply-To: <20200622220518.Horde.wiJxNPDxmPl65JMVmIXHgrP@webmail.leidinger.net> References: <20200622220518.Horde.wiJxNPDxmPl65JMVmIXHgrP@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander, Thank you so much for the advice. I have sent the email to freebsd-net@. No response yet (I just sent it). -Neel Chauhan https://www.neelc.org/ On 2020-06-22 13:05, Alexander Leidinger via freebsd-hackers wrote: > Quoting Neel Chauhan <neel@neelc.org> (from Fri, 19 Jun 2020 21:02:00 > -0700): > >> Hi, >> >> I have many patches, focusing on the TCP/IP stack on Phabricator. >> >> Some of them are accepted, but not committed. Most are stuck as needs >> review. And many of these patches are only a few lines/trivial. >> >> For instance, on my Phabricator: >> >> * My account: https://reviews.freebsd.org/p/neel_neelc.org/ >> * My patches: https://reviews.freebsd.org/people/revisions/5933/ >> >> Would these patches get reviewed eventually? Is there anything I can >> do to speed up the process? Or is this something I need to be patient >> about? > > What helps is to send a mail to freebsd-net@freebsd.org and to ask for > review/commit. Include a little description of what your patch > fixes/improves. If this doesn't result in a respose, you can also have > a look at the commit log of the area you patch, and send a few people > which worked in this area recently a mail and ask if they could have > a review of your patch. > > Bye, > Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fb71e5ec139be0178f11abb9eb15b305>