Re: What's cooking in git.git (Dec 2012, #03; Wed, 12)

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Dec 15, 2012, 09:24 UTC
Message-ID: <CAMP44s0ou-8u1N7k8U9qHfagFJR4Jn6HYWZ8_jWgXgRUuzUJEQ@mail.gmail.com>
In-Reply-To: <CACsJy8A=-3-C29LKQasfUih24cSZrRuQRJ28WjP0zKg=NaFuUA@mail.gmail.com>

On Sat, Dec 15, 2012 at 2:44 AM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:

> On Sat, Dec 15, 2012 at 2:45 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:

Show 7 quoted lines

>>> Cruft in the codebase is a problem for git *developers* because it makes
>>> the code harder to maintain and extend.
>>
>> A problem big enough to warrant the rejection of the patch series? No.
>
> May I suggest you maintain remote-bzr as a separate project? You have
> total control that way without anyone's disagreeing with you.

Which disagreement? We have all agreed how the code should look like in the end. The disagreement is on how and when this code should be merged to git.git. A separate project is not going to help there.

> And speaking from someone whose series may take months to get
> in, why the rush?

Why the delay? Junio had already merged this code to 'next'.

-- 
Felipe Contreras