From owner-freebsd-hackers@FreeBSD.ORG  Sun Nov 18 10:49:01 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 8B864CD9;
 Sun, 18 Nov 2012 10:49:01 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 7C1E68FC0C;
 Sun, 18 Nov 2012 10:48:59 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA01458;
 Sun, 18 Nov 2012 12:48:50 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1Ta2Qk-0008x9-Dt; Sun, 18 Nov 2012 12:48:50 +0200
Message-ID: <50A8BD0F.7030609@FreeBSD.org>
Date: Sun, 18 Nov 2012 12:48:47 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:16.0) Gecko/20121030 Thunderbird/16.0.2
MIME-Version: 1.0
To: Adrian Chadd <adrian@FreeBSD.org>
Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]
References: <CAD2Ti29UoFcHendR8CcdQ4FPNW1HH0O47B1i3JW00Lke2m2POg@mail.gmail.com>
 <20121117221143.41c29ba2@nonamehost> <op.wnxq9eo0g7njmm@michael-think>
 <CADLo838oG26KmfHJ+tLh82GoJzzRtfqy69+Nny1_DC8F8X4POQ@mail.gmail.com>
 <50a8eb34.5pMwq6kSsi47QgKI%perryh@pluto.rain.com>
 <20121118073128.GG73505@kib.kiev.ua>
 <CAJ-Vmom6+S3HDuOF6woWyvST1JVPjwV6GUs2RJGtfD_z_YVNDA@mail.gmail.com>
In-Reply-To: <CAJ-Vmom6+S3HDuOF6woWyvST1JVPjwV6GUs2RJGtfD_z_YVNDA@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-hackers@FreeBSD.org,
 Perry Hutchison <perryh@pluto.rain.com>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Nov 2012 10:49:01 -0000

on 18/11/2012 10:15 Adrian Chadd said the following:
> 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.

What you describe is not a workflow issue, but a local development
environment(s) setup issue.


-- 
Andriy Gapon