Re: What's in git.git

From: Junio C Hamano <junkio@cox.net>
Date: Sep 18, 2006, 08:19 UTC
Message-ID: <7vmz8xr3ij.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0609181010500.19042@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 13 quoted lines

>> > That's not a good excuse, though.  It means you cannot propose
>> > new core-side support that only gitweb would benefit from
>> > initially, since we will not add new stuff to the core that does
>> > not have real users, and new stuff in the core must be cooked in
>> > "next" before it is proven to be useful and correct.
>>  
>> But this also means that if I were for example to use git-for-each-ref
>> in gitweb, I couldn't _test_ if it works. Ah, well, if you can live with
>> PATCH/RFC... But I'd rather wait for git-for-each-ref in _released_ version
>> of git. 
>
> Why not set up a testing directory, where you use both gitweb _and_ git 
> from next? It is easy...

That's Ok; it means that he just cannot work on certain things. It's not like we take gitweb patch only from Jakub, so it is not the end of the world either ;-).

Also it is handy to have somebody who sticks to things that are available in master to catch breakage we might accidentally cause by Porcelainish commands jumping the gun before core-side change hits the master branch.