Date: Sun, 18 Nov 2012 00:15:12 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-hackers@freebsd.org, Perry Hutchison <perryh@pluto.rain.com> Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident] Message-ID: <CAJ-Vmom6%2BS3HDuOF6woWyvST1JVPjwV6GUs2RJGtfD_z_YVNDA@mail.gmail.com> In-Reply-To: <20121118073128.GG73505@kib.kiev.ua> References: <CAD2Ti29UoFcHendR8CcdQ4FPNW1HH0O47B1i3JW00Lke2m2POg@mail.gmail.com> <20121117221143.41c29ba2@nonamehost> <op.wnxq9eo0g7njmm@michael-think> <CADLo838oG26KmfHJ%2BtLh82GoJzzRtfqy69%2BNny1_DC8F8X4POQ@mail.gmail.com> <50a8eb34.5pMwq6kSsi47QgKI%perryh@pluto.rain.com> <20121118073128.GG73505@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 November 2012 23:31, Konstantin Belousov <kostikbel@gmail.com> wrote: > Git would work well with our workflow. It supports the centralized > repository model, which the project employs right now. It may work with your workflow, but it doesn't work with mine. :-) Right now the source tree isn't very good at building drivers from a full HEAD checkout on a -9 or -8 running system. The include paths end up pulling from the local sys/net directory, for example, rather than falling through to the specified kernel build and kernel source path. So at least for me, working almost exclusively in driver/stack land, I can do sparse check out of only the bits that I'm working on. It lets me get work done without having to run an up to date -HEAD (and keep said install up to date.) I also do development on little old netbooks with SSDs that would make it prohibitive to checkout multiple git trees. No, using git on a USB/CF/etc card doesn't work very well either I'm afraid. I'm sure there are other use cases. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom6%2BS3HDuOF6woWyvST1JVPjwV6GUs2RJGtfD_z_YVNDA>