From: Jonathan Nieder <jrnieder@gmail.com>
Date: Sat, 19 Feb 2011 00:50:30 GMT
Subject: Re: [RFC/PATCH 0/3] Thinning the git toplevel directory
Message-ID: <20110219005030.GB27316@elie>
In-Reply-To: <7v39nkooem.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:

>> - build result - objects, final binaries, generated documentation etc 
>>   The advantage besides unclutterting is possibility to have sources on
>>   read-only medium.
>
> This is somewhere between a meh to mild nak.  "git grep" knows to ignore
> untracked cruft, so this does not help nor hinder "finding" at all. Even
> though I personally tend to value seeing frotz.o sitting immediately next
> to frotz.c, some people may value read-only source tree more than that.

At the risk of becoming repetitive: it is quite possible for make to
take an O=elsewhere/ parameter to support both types.

I am also in the camp of preferring to see frotz.o next to frotz.c.
After editing frotz.c, I can do "make frotz.o" to make sure it still
compiles.