From owner-freebsd-hackers@FreeBSD.ORG  Sun Nov 18 07:13:05 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 96FB75AE
 for <freebsd-hackers@freebsd.org>; Sun, 18 Nov 2012 07:13:05 +0000 (UTC)
 (envelope-from perryh@pluto.rain.com)
Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34])
 by mx1.freebsd.org (Postfix) with ESMTP id 6770C8FC13
 for <freebsd-hackers@freebsd.org>; Sun, 18 Nov 2012 07:13:05 +0000 (UTC)
Received: from agora.rdrop.com (66@localhost [127.0.0.1])
 by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id qAI7D3bQ013566
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
 Sat, 17 Nov 2012 23:13:03 -0800 (PST)
 (envelope-from perryh@pluto.rain.com)
Received: (from uucp@localhost)
 by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id qAI7D3wO013565;
 Sat, 17 Nov 2012 23:13:03 -0800 (PST)
 (envelope-from perryh@pluto.rain.com)
Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com
 (4.1/SMI-4.1-pluto-M2060407) id AA25429; Sat, 17 Nov 12 23:06:01 PST
Date: Sat, 17 Nov 2012 23:05:40 -0800
From: perryh@pluto.rain.com (Perry Hutchison)
To: utisoft@gmail.com
Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]
Message-Id: <50a8eb34.5pMwq6kSsi47QgKI%perryh@pluto.rain.com>
References: <CAD2Ti29UoFcHendR8CcdQ4FPNW1HH0O47B1i3JW00Lke2m2POg@mail.gmail.com>
 <20121117221143.41c29ba2@nonamehost> <op.wnxq9eo0g7njmm@michael-think>
 <CADLo838oG26KmfHJ+tLh82GoJzzRtfqy69+Nny1_DC8F8X4POQ@mail.gmail.com>
In-Reply-To: <CADLo838oG26KmfHJ+tLh82GoJzzRtfqy69+Nny1_DC8F8X4POQ@mail.gmail.com>
User-Agent: nail 11.25 7/29/05
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: fidaj@ukr.net, gmx@ross.cx, grarpamp@gmail.com, freebsd-hackers@freebsd.org
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 07:13:05 -0000

[trimmed some of the lists]

Chris Rees <utisoft@gmail.com> wrote:
> ... git doesn't work with our workflow.

I'm sure the workflow itself is documented somewhere, but is
there a good writeup of _how_ git doesn't work with it, e.g. what
capabilit{y,ies} is/are missing?  Seems this might be of interest
to the git developers, not because they necessarily want to support
FreeBSD as such, but as an example of a real-world workflow that git
currently does not handle well.