From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's (not) cooking
Date: Fri, 06 Jul 2018 15:57:56 -0700 [thread overview]
Message-ID: <xmqqlgaogeff.fsf@gitster-ct.c.googlers.com> (raw)
I'll be pushing out the integration branches with some updates, but
there is no change in 'next' and below. The following topics I gave
a quick look and gave them topic branches, but I had trouble merging
them in 'pu' and making them work correctly or pass the tests, so
they are not part of 'pu' in today's pushout.
pk/rebase-in-c
en/dirty-merge-fixes
en/t6036-merge-recursive-tests
en/t6042-insane-merge-rename-testcases
ds/multi-pack-index
next reply other threads:[~2018-07-06 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 22:57 Junio C Hamano [this message]
2018-07-06 23:07 ` What's (not) cooking Junio C Hamano
2018-07-07 2:16 ` Elijah Newren
2018-07-07 12:11 ` Johannes Schindelin
2018-07-07 15:34 ` Elijah Newren
2018-07-07 22:54 ` Kim Gybels
2018-07-07 12:08 ` Johannes Schindelin
2018-07-09 13:50 ` Derrick Stolee
2018-07-09 16:13 ` Junio C Hamano
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=xmqqlgaogeff.fsf@gitster-ct.c.googlers.com \
--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).