Re: [PATCH 0/3] a small branch API clean-up

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 21, 2017, 08:52 UTC
Message-ID: <xmqqtvysg9w8.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <1508555222.2516.11.camel@gmail.com>

Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:

Show 12 quoted lines

> On Fri, 2017-10-13 at 14:11 +0900, Junio C Hamano wrote:
>> This started as a little clean-up for a NEEDSWORK comment in
>> branch.h, but it ended up adding a rather useful safety feature.
>> 
>
> Part of this series seems to duplicate the work done in part of my
> series that tries to give more useful error messages when renaming a
> branch.
>
> https://public-inbox.org/git/%3C20170919071525.9404-1-kaarticsivaraam91196@gmail.com%3E/
>
> Any reasons for this?

Sorry, but I am not sure what you are asking.

I was looking at the code, noticed NEEDSWORK comment and worked on cleaning things up---you seem to feel that I need a reason, or perhaps even your permission, when I try improving the codebase? That starts to sound a bit ridiculous.

As different developers are multiple people, it just happens that areas somebody changes overlap an area somebody else wants to change. It's not like anybody owns a piece of source file when s/he expresses an interest to work on something that may or may not affect that area.