Re: What's cooking in git.git (topics)

From: Alex Riesen <raa.lkml@gmail.com>
Date: Apr 19, 2007, 00:23 UTC
Message-ID: <20070419002357.GC14247@steel.home>
In-Reply-To: <7v647tcjr6.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano, Thu, Apr 19, 2007 02:04:13 +0200:

Show 9 quoted lines

> 
> Stalled; Alex has a set of tests that should go on top of this
> series but I haven't taken a look at it yet.  I think we should
> have enough for interested people to start futzing with, and I
> am wondering why nobody has sent a note saying "Hey, I did this
> using tree objects with commits in it, it works nicely for these
> operations but these things are still cumbersome to do and I
> need to polish it more".
>

I am setting up a super-repo for my own very private use (small home server setup). Still working on what _recursive_ tools do I really need (and fsck is not the most interesting one: git-diff-files is. Am afraid of releasing a system I wont ever be able to get to the source of).

It is, as predicted, becoming mostly work on build infrastructure and integrity checks in the super-project. Being the sole user of this project I'll definitely miss all the issues of really big modularized projects, though.

Show 7 quoted lines

> 
> * jc/the-index (Sun Apr 1 23:26:07 2007 -0700) 2 commits
>  - Make read-cache.c "the_index" free.
>  - Move index-related variables into a structure.
> 
> A small part of libification; nobody seems to want it.
>

No user _can_ want it. We need to make the future less a nightmare (it may not even become one).