Date: Tue, 27 Mar 2018 13:45:12 -0700 From: Warner Losh <imp@bsdimp.com> To: Lakhan Shiva <lakhanshiva@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Commit privileges and branching Message-ID: <CANCZdfrghEpcopgKfBwU4jzzbj6u5R=TttA08EJ7iRaD-Pk0%2BA@mail.gmail.com> In-Reply-To: <CAHC0Ygfs0cjXDAnaVUKnZHqm%2BqJvb8UBJyDsSwbzO3gC%2Bs-tGw@mail.gmail.com> References: <CAHC0Ygfs0cjXDAnaVUKnZHqm%2BqJvb8UBJyDsSwbzO3gC%2Bs-tGw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Tue, Mar 27, 2018 at 9:42 AM, Lakhan Shiva <lakhanshiva@gmail.com> wrote: > Hi, > > I would like to start working on converting PCI drivers that already have a > table but font have a MODULE_PNP_INFO. I would like to know more about the > branching strategy and the process to check in first piece of code. I am > uising FreeBSD VM current image. I will be using SVN for checking out and > checking in code from the VM. > There's two paths forward for you. If you are selected for GSoC, you'll have our gsoc svn repo available. The other option is to fork from http://www.github.org/freebsd/freebsd using git. The way that commits normally land in the FreeBSD is that some committer will push them in with a tag saying that you'd submitted it and when there's enough you'd get a commit bit of all has gone well. If you're doing GSoC, then you and your mentor would work this out. Warnerhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrghEpcopgKfBwU4jzzbj6u5R=TttA08EJ7iRaD-Pk0%2BA>