From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?UmVuw6kgU2NoYXJmZQ==?= Subject: Re: What's cooking in git.git (Jun 2012, #01; Sun, 3) Date: Sun, 10 Jun 2012 19:39:35 +0200 Message-ID: <4FD4DBD7.5070204@lsrfire.ath.cx> References: <7vr4twudqm.fsf@alter.siamese.dyndns.org> <7vbokwmifp.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Junio C Hamano , git@vger.kernel.org To: Felipe Contreras X-From: git-owner@vger.kernel.org Sun Jun 10 19:39:55 2012 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 1Sdm7E-0008IG-Ol for gcvg-git-2@plane.gmane.org; Sun, 10 Jun 2012 19:39:53 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754215Ab2FJRjt convert rfc822-to-quoted-printable (ORCPT ); Sun, 10 Jun 2012 13:39:49 -0400 Received: from india601.server4you.de ([85.25.151.105]:40161 "EHLO india601.server4you.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754128Ab2FJRjs (ORCPT ); Sun, 10 Jun 2012 13:39:48 -0400 Received: from [192.168.2.105] (p4FFD867F.dip.t-dialin.net [79.253.134.127]) by india601.server4you.de (Postfix) with ESMTPSA id 4561B2F8056; Sun, 10 Jun 2012 19:39:46 +0200 (CEST) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Am 06.06.2012 20:17, schrieb Felipe Contreras: > On Wed, Jun 6, 2012 at 7:58 PM, Junio C Hamano wr= ote: >> Felipe Contreras writes: >> >>>> The last remaining sticking point is what to do with the duplicate= d shell >>>> function. >>> >>> What is the problem with leaving it as it is; having it as a duplic= ate >>> function. It's not a *huge* maintenance burden, and it's a big prob= lem >>> if the functions diverge. In the last sentence you say that there would be a "big problem". >> It is not even funny to see these two conflicting claims made in a >> single sentence. Given that you are aware that it will cause a huge >> problem to the end users if they diverge, > > What would be that *huge* problem? Here you ask what's so bad about it. Perhaps you meant to write "it's NOT a big problem" in the first place? Ren=C3=A9