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

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Dec 15, 2012, 08:44 UTC
Message-ID: <CACsJy8A=-3-C29LKQasfUih24cSZrRuQRJ28WjP0zKg=NaFuUA@mail.gmail.com>
In-Reply-To: <CAMP44s0=R3rdnD-Zpzz_7wY6HKKsAL1sPVYh4pc3z1CBbX2ODg@mail.gmail.com>

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

Show 9 quoted lines

> Couple of facts first:
> a) This code was already merged
> b) This code is for a test
> c) I'm the only developer so far
>
>> 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. So you may be more productive and we have less of these emails back and forth. And speaking from someone whose series may take months to get in, why the rush?

-- 
Duy