From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's _not_ cooking in git.git yet
Date: Sun, 20 Jul 2008 23:33:33 -0700 [thread overview]
Message-ID: <7vy73vvj9e.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vtzejx0q1.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 20 Jul 2008 22:31:02 -0700")
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.
prev parent reply other threads:[~2008-07-21 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 5:31 What's cooking in git.git (2008-07 issue #9) Junio C Hamano
2008-07-21 6:33 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy73vvj9e.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).