From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Adam Spiers" <git@adamspiers.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: No "What's cooking" yet, but...
Date: Mon, 15 Apr 2013 00:26:58 -0700 [thread overview]
Message-ID: <7vvc7o1cfx.fsf@alter.siamese.dyndns.org> (raw)
I've merged a handful more topics to 'next'.
It is likely that I'll be merging kb/status-ignored-optim to
'master' soonish, but as I kept saying this topic touches rather
core part of working tree inspection code, so a fallout from it may
affect not just "status -u<various>" but more destructive "add",
"rm". A final eyeballing of the topic is very much appreciated.
Also I've ejected nd/magic-pathspecs and as/check-ignore topics from
'pu' for now, as the former when taken with jl/submodule-mv were
somehow breaking the tests (I was running the integration run for
'pu' without 5301, 5700, 7001 and 7408 for a few days), and the
latter topic did not play well with kb/status-ignored-optim topic.
We may want to revisit them after having a few more topics graduate
to 'master' first and then ask them to be rebased.
Thanks.
reply other threads:[~2013-04-15 7:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7vvc7o1cfx.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@adamspiers.org \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).