Date: Fri, 1 Mar 2013 06:38:18 -0800 From: Josh Paetzel <josh@tcbug.org> To: "Duvvuru,Venkat Kumar" <VenkatKumar.Duvvuru@Emulex.Com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: OCE driver patches Message-ID: <E59FC35E-9111-4667-B0D7-0D716C2F4DF8@tcbug.org> In-Reply-To: <BF3270C86E8B1349A26C34E4EC1C44CB215D84F9@CMEXMB1.ad.emulex.com> References: <BF3270C86E8B1349A26C34E4EC1C44CB215A0220@CMEXMB1.ad.emulex.com> <B3A73C45-3299-4EDD-BE38-9D027E9D548A@tcbug.org> <BF3270C86E8B1349A26C34E4EC1C44CB215D84F9@CMEXMB1.ad.emulex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 1, 2013, at 5:36 AM, "Duvvuru,Venkat Kumar" <VenkatKumar.Duvvuru@Emulex.Com> wrote: > Hi Josh, > I have a bunch of patches (~25 in number) to submit. Please let me know the process to submit them. > Do I just attach them in a single email or open pr's for each of them?? > Pls suggest. > > /Venkat > Venkat, I think it depends on how you want them committed to FreeBSD. If the patches are atomic changes that should be kept atomic in the FreeBSD source tree then I'll commit them seperately. This is a tad time consuming as I test them atomically before committing them. If they can be committed in one go then I can just apply them all, test the end result, and commit that. One PR with the patches attached and a note saying these can all go in in one go is appropriate in the latter case, the former would be best served by seperate PRs. Thanks, Josh Paetzel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E59FC35E-9111-4667-B0D7-0D716C2F4DF8>