From owner-freebsd-hackers@freebsd.org Fri Sep 13 14:05:46 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 059A6F26C3 for ; Fri, 13 Sep 2019 14:05:46 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46VHV11TVTz3C3D for ; Fri, 13 Sep 2019 14:05:44 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id C61F93C0199; Fri, 13 Sep 2019 14:05:43 +0000 (UTC) Date: Fri, 13 Sep 2019 14:05:43 +0000 From: Brooks Davis To: Mihir Luthra Cc: freebsd-hackers@freebsd.org Subject: Re: correct ways to get code reviewed Message-ID: <20190913140543.GC93439@spindle.one-eyed-alien.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-Rspamd-Queue-Id: 46VHV11TVTz3C3D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of brooks@spindle.one-eyed-alien.net has no SPF policy when checking 199.48.129.229) smtp.mailfrom=brooks@spindle.one-eyed-alien.net X-Spamd-Result: default: False [-6.49 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-3.59)[ip: (-9.37), ipnet: 199.48.128.0/22(-4.67), asn: 36236(-3.86), country: US(-0.05)]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[freebsd.org]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[brooks@freebsd.org,brooks@spindle.one-eyed-alien.net]; SIGNED_PGP(-2.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US]; FROM_NEQ_ENVFROM(0.00)[brooks@freebsd.org,brooks@spindle.one-eyed-alien.net]; RCVD_COUNT_ZERO(0.00)[0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2019 14:05:46 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 13, 2019 at 11:49:23AM +0530, Mihir Luthra wrote: > Hi everyone, >=20 > I am a new contributor to FreeBSD projects. Recently I have started making > changes in the source code by working on project ipv6 userland cleanup [1= ]. > I did post one patch to phabrictor which got reviewed as well. >=20 > I had some queries in my mind on which I wanted some advice. > 1) Should I post another patch only after the first one has been approved > or is it better to keep posting patches irrespective of review status of > the first? It's fine to post multiple patches. If you have multiple patches that depend on each other you may find it useful to post both to let reviewers see the bigger picture. > 2) Should I ask commiters for review individually or should I post the li= nk > on the mailing lists? Or maybe should I simply wait for the patch to get > reviewed without informing anyone? Asking individual committers is a good approach if you can identify an active committers in the area. Mailing lists can also work. I don't recommend posting patching and hoping someone reviews them. That's all too likely to result in them being dropped. > 3) If the patch gets approved, do I need to submit a pul request on github > or is their some different procedure? If a patch is approved, you should ask the reviewer(s) to commit it. Can easily use "arc patch" to apply it and commit it. -- Brooks --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJde6I2AAoJEKzQXbSebgfANTsH/i936fAJOUWM4tJRReB7hCl2 UGBsVwCdv1lVkS9W6ogMapzj+tglJqBVC60C+Jq/Qu8TpoSmPS6frcuSgZ6ulMyo uj7G0h6n+tqDAHJS5ZuyCiV/AD09BzOlEFHCwQkM9wNWRVlDVHjqL7CN3tTMTMhO Nib3tRwg9mO5ILo1k9Rt+gATJn+UzMNQ8FRAiXA2w9MjhKL0uGKPLXcQWUbcDcmS zOHDVes0f3TJa5dpcGqXmqndFeeJApqtN41VW2AKJ3Qh81kCZsOBzjsamXieeUiP XuZ0QtOjxNn/Df1BuInnTeAVpbC7BIP/3MgsJkpjYfrpL+ehbHI7Z79cAsS7HhA= =bk3w -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP--