From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 23:13:08 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE673106566B for ; Sat, 11 Sep 2010 23:13:08 +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 BA5C08FC14 for ; Sat, 11 Sep 2010 23:13:08 +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 o8BND8lc014819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Sep 2010 16:13:08 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id o8BND89Z014817; Sat, 11 Sep 2010 16:13:08 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA18648; Sat, 11 Sep 10 16:11:44 PDT Date: Sat, 11 Sep 2010 16:11:48 -0700 From: perryh@pluto.rain.com To: aryeh.friedman@gmail.com Message-Id: <4c8c0cb4.n0Z+r+TIC4vzdXnS%perryh@pluto.rain.com> References: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 23:13:08 -0000 Aryeh Friedman wrote: > I would prefer to have the plain text around after a power failure > because it could be several days of work ... Ideally there should be _some_ mechanism for committing unfinished work to a (probably encrypted) repository on, at least, a daily basis. The more I see of this thread, the more it seems that the problem is largely the fault of the particular VCS being used. A VCS that demands a "review" step before anything can be checked in, even on a "work in progress" branch as opposed to the mainline, seems a poor fit for a project in which developers are not permitted to see one anothers code.