From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl Worth Subject: Re: git-status too verbose? Date: Mon, 06 Mar 2006 09:46:48 -0800 Message-ID: <87irqrzcs7.wl%cworth@cworth.org> References: <38b80e980603040952j15152a21h2c903bd011d7e905@mail.gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Mon_Mar__6_09:46:41_2006-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Cc: git@vger.kernel.org X-From: git-owner@vger.kernel.org Mon Mar 06 18:48:54 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FGJov-0005Mi-Of for gcvg-git@gmane.org; Mon, 06 Mar 2006 18:48:34 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751968AbWCFRsa (ORCPT ); Mon, 6 Mar 2006 12:48:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751972AbWCFRsa (ORCPT ); Mon, 6 Mar 2006 12:48:30 -0500 Received: from theworths.org ([217.160.253.102]:38843 "EHLO theworths.org") by vger.kernel.org with ESMTP id S1751968AbWCFRsa (ORCPT ); Mon, 6 Mar 2006 12:48:30 -0500 Received: (qmail 7974 invoked from network); 6 Mar 2006 12:48:29 -0500 Received: from localhost (HELO raht.cworth.org) (127.0.0.1) by localhost with SMTP; 6 Mar 2006 12:48:29 -0500 To: "Eric Jaffe" In-Reply-To: <38b80e980603040952j15152a21h2c903bd011d7e905@mail.gmail.com> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.4 Mule/5.0 (SAKAKI) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: --pgp-sign-Multipart_Mon_Mar__6_09:46:41_2006-1 Content-Type: text/plain; charset=US-ASCII On Sat, 4 Mar 2006 12:52:17 -0500, "Eric Jaffe" wrote: > I was wondering if anyone else thinks that git-status should be more > like "git-diff --name-status". That is, > # A a/newfile.c > # M a/oldfile.c Something like that does seem appealing. There are at least two issues with doing it: 1) It might be tricky coming up with canonical single characters to be used consistently within git. For example, git-ls-files currently does do some single-character state indication, but it can be rather confusing at times. For example: State Option Character ----- ------ --------- Modified -m C Unmerged -u M Cached -c H And that looks like a permanent problem. For legacy reasons, I don't think we can change either the options or the output characters of git-ls-files. But perhaps we could at least agree on a single, consistent mapping for all future uses. 2) In an important sense, git-status is not verbose enough. For example, given a single line such as the following: modified: some-file This could indicate at least two different states for some-file: 1) Modified and updated into the index 2) Modified in working tree, but not updated in the index Currently, git-status makes this distinction only in the header lines for the separate chunks of its output. But, when there are a lot of files involved, and things start scrolling, it's sometimes "hard" to associate the right header with the file of interest. So, what I've wanted from git-status is a complete encoding of the file's state on the same line as the output of the filename. Maybe something that uses two characters per file would work well. But I don't have a concrete suggestion for that---I don't think I've even successfully enumerated all possible file states with git yet... -Carl PS. If we do tighten up the output of git-status, I'd also vote for making the per-chunk headers use only 1 line each instead of 2, and also eliminating the second blank line separating each chunk. --pgp-sign-Multipart_Mon_Mar__6_09:46:41_2006-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBEDHWH6JDdNq8qSWgRAm7HAKCbm1LL742zbS+E4iNTd0IGN0naOQCeJw26 M1EwLogABbB9qQAHq9ZbLJo= =GeSs -----END PGP SIGNATURE----- --pgp-sign-Multipart_Mon_Mar__6_09:46:41_2006-1--