Re: What's cooking in git.git (topics)
- From
Alex Riesen <raa.lkml@gmail.com>
- Date
- Apr 20, 2007, 11:58 UTC
- Message-ID
- <81b0412b0704200458n33c1eb83p540b738e7ff26ec9@mail.gmail.com>
- In-Reply-To
- <7vmz13z4au.fsf@assigned-by-dhcp.cox.net>
On 4/20/07, Junio C Hamano <junkio@cox.net> wrote:
> Making git.git the first guinea pig has a unique bootstrapping > problem involved, however. These kind of changes in git.git > itself has to wait at least until what we have in 'next' today > is in everybody's hands.
Have you any plans as to when that should begin to happen? We can warn user if he tries to add a subproject until porcelain support can be considered usable. It certainly wont be a problem for early adopters, they know what they're doing, and an accidental git add of a directory (which by accident is a git repo all by itself) does not go unnoticed. Or even disallow it by default (unset dir_struct:dir_links), and give git add/update-index an option to allow them. We can reconsider the default later.