What's _not_ cooking in git.git yet
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 21, 2008, 06:33 UTC
- Message-ID
- <7vy73vvj9e.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <7vtzejx0q1.fsf@gitster.siamese.dyndns.org>
There are a few topics that are still not ready but should be in the -rc1.
* I want Pasky's "saner git-mv" to be in if possible, although I am moderately pessimistic about the submodule work that comes on top of it.
* "optimize ssh connection for throughput not for latency" may be a worthy goal, but I think the point Jeff raised about the shared connection is a valid concern. It might be better not to do anything funky at the software level, but just add an entry in tips&tricks section of gitwiki.
Other than that, we should be focused more on fixes on regressions (if any), fixes in new features added in v1.6.0 cycle, than adding not-yet-in features nor code clean-ups.
I'll switch my production branch to 'master' tonight. I expect active contributors to do the same and keep it that way until 1.6.0 final. Right now, with 'merge -Xtheirs' removed, the difference between 'master' and 'next' is extremely thin.
Thanks.