From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Pitre Subject: Re: 'git status' is not read-only fs friendly Date: Sat, 10 Feb 2007 13:51:08 -0500 (EST) Message-ID: References: <7vr6syj7uw.fsf@assigned-by-dhcp.cox.net> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: Junio C Hamano , Johannes Schindelin , Marco Costalba , GIT list To: Linus Torvalds X-From: git-owner@vger.kernel.org Sat Feb 10 19:51:16 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1HFxJa-0006mI-Hn for gcvg-git@gmane.org; Sat, 10 Feb 2007 19:51:14 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751769AbXBJSvK (ORCPT ); Sat, 10 Feb 2007 13:51:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751766AbXBJSvK (ORCPT ); Sat, 10 Feb 2007 13:51:10 -0500 Received: from relais.videotron.ca ([24.201.245.36]:30987 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751769AbXBJSvJ (ORCPT ); Sat, 10 Feb 2007 13:51:09 -0500 Received: from xanadu.home ([74.56.106.175]) by VL-MH-MR001.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0JD900FPIGD8RY00@VL-MH-MR001.ip.videotron.ca> for git@vger.kernel.org; Sat, 10 Feb 2007 13:51:08 -0500 (EST) In-reply-to: X-X-Sender: nico@xanadu.home Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On Sat, 10 Feb 2007, Linus Torvalds wrote: > It is *not* a read-only operation. The index is too important to be > considered "just a technical issue". There is just a semantic issue that you seem to overlook completely. According to the dictionarry, "status" is a synonym to a "state". It is _not_ an action. So, from a _user_ perspective, the git-status command should give back a "status". Of _course_ the user will benefit from the index updating business, but as important as this update might be (and I do agree that it is fundamental for GIT's performance), this is still a by-product of the "status" command. Therefore, the fact that the index isn't writable should not prevent git-status from providing the very result for which its name was chosen. The index might as well be brought up to date on disk the next time the file system is writable. Nicolas