From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Philip Oakley" Subject: Re: Git's inconsistent command line options Date: Wed, 26 Aug 2015 23:52:19 +0100 Organization: OPDS Message-ID: <500FC504AB174A98B31CD8BEFCDDCFAC@PhilipOakley> References: Reply-To: "Philip Oakley" Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit Cc: "Hilco Wijbenga" , "Stefan Beller" , "Graeme Geldenhuys" , "Git Mailing List" To: "Jacob Keller" , "Junio C Hamano" X-From: git-owner@vger.kernel.org Thu Aug 27 00:51:42 2015 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZUjXh-0008Hb-4A for gcvg-git-2@plane.gmane.org; Thu, 27 Aug 2015 00:51:41 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757132AbbHZWvh (ORCPT ); Wed, 26 Aug 2015 18:51:37 -0400 Received: from out1.ip05ir2.opaltelecom.net ([62.24.128.241]:26425 "EHLO out1.ip05ir2.opaltelecom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756895AbbHZWvg (ORCPT ); Wed, 26 Aug 2015 18:51:36 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DwEgC2Qd5VPDWzBlxdGQEBAYJ/gT2DI4Mubb4uBAQCgTdNAQEBAQEBBwEBAQFBJBtBBINZBQEBAQEDCAEBGRUeAQEhCwIDBQIBAxUDAgIFIQICFAEECBIGBwMUBgESCAIBAgMBCod+Axa0H4ZYiHINhVyBIoo5gk+CO4JwL4EUBZU5AYETiS1EgzcVhzuGeYMQhzuCNRyBVT0zgk0BAQE X-IPAS-Result: A2DwEgC2Qd5VPDWzBlxdGQEBAYJ/gT2DI4Mubb4uBAQCgTdNAQEBAQEBBwEBAQFBJBtBBINZBQEBAQEDCAEBGRUeAQEhCwIDBQIBAxUDAgIFIQICFAEECBIGBwMUBgESCAIBAgMBCod+Axa0H4ZYiHINhVyBIoo5gk+CO4JwL4EUBZU5AYETiS1EgzcVhzuGeYMQhzuCNRyBVT0zgk0BAQE X-IronPort-AV: E=Sophos;i="5.17,419,1437433200"; d="scan'208";a="616844564" Received: from host-92-6-179-53.as43234.net (HELO PhilipOakley) ([92.6.179.53]) by out1.ip05ir2.opaltelecom.net with SMTP; 26 Aug 2015 23:51:34 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: From: "Jacob Keller" > On Wed, Aug 26, 2015 at 10:56 AM, Junio C Hamano > wrote: >> But notice that I said "if you really want to". I personally think >> it is a road to madness. > > Agreed. I don't believe in command line API here. I think we'd need a > better solution. > > My gut says: Live with the warts on old commands and try to make > people use command words for new commands. > -- Agreed. However Graeme's original question also said "I can supply a more extensive list if needed", and "I still have to reference the help to remind me of what parameter to use in certain situation", which suggests that one option is to capture that list within some part of the documentation, especially if Graeme already has an easy to read layout. If it could be part of the documenation, where should it go - gitcli or perhaps it's own guide (`git help -g` and friends)? -- Philip