From: Felipe Contreras <felipe.contreras@gmail.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2012, #01; Sun, 3)
Date: Mon, 11 Jun 2012 12:27:02 +0200 [thread overview]
Message-ID: <CAMP44s1ESu0WKYmR6g51q3cwJ-BWC22SuTHucGVSEsGuGTrxDQ@mail.gmail.com> (raw)
In-Reply-To: <4FD4DBD7.5070204@lsrfire.ath.cx>
On Sun, Jun 10, 2012 at 7:39 PM, René Scharfe
<rene.scharfe@lsrfire.ath.cx> wrote:
> Am 06.06.2012 20:17, schrieb Felipe Contreras:
>
>> On Wed, Jun 6, 2012 at 7:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>>
>>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>>
>>>>> The last remaining sticking point is what to do with the duplicated
>>>>> shell
>>>>> function.
>>>>
>>>>
>>>> What is the problem with leaving it as it is; having it as a duplicate
>>>> function. It's not a *huge* maintenance burden, and it's a big problem
>>>> 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?
Yeap, that's what I meant.
--
Felipe Contreras
prev parent reply other threads:[~2012-06-11 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 0:23 What's cooking in git.git (Jun 2012, #01; Sun, 3) Junio C Hamano
2012-06-06 12:22 ` Felipe Contreras
2012-06-06 17:58 ` Junio C Hamano
2012-06-06 18:17 ` Felipe Contreras
2012-06-10 7:26 ` Junio C Hamano
2012-06-10 15:09 ` Felipe Contreras
2012-06-11 14:54 ` Junio C Hamano
2012-06-13 14:55 ` Felipe Contreras
2012-06-13 17:19 ` Junio C Hamano
2012-06-13 18:04 ` Felipe Contreras
2012-06-10 17:39 ` René Scharfe
2012-06-11 10:27 ` Felipe Contreras [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s1ESu0WKYmR6g51q3cwJ-BWC22SuTHucGVSEsGuGTrxDQ@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).