From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Derrick Stolee" <dstolee@microsoft.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Preparing for 2.20.1 brown-paper-bag maintenance release
Date: Thu, 13 Dec 2018 15:29:27 +0900 [thread overview]
Message-ID: <xmqq4lbiey7s.fsf@gitster-ct.c.googlers.com> (raw)
Here is an excerpt from a draft edition of "What's cooking" report
for topics that are about an immediate 2.20.1 maintenance release,
with five topics that I plan to merge to 'next' and then to 'maint'
soonish (they're all marked as "Will merge to 'next' and then to
'master'").
They'll be in 'pu' but not in 'next' in today's pushout, but unless
I hear breakage reports in time, I am hoping to merge them to 'next'
during tomorrow's integration cycle, so that we can start the new
week with 2.20.1.
Thanks.
--------------------------------------------------
* ds/hash-independent-tests-fix (2018-12-12) 1 commit
- .gitattributes: ensure t/oid-info/* has eol=lf
Test portability fix.
* jc/run-command-report-exec-failure-fix (2018-12-12) 1 commit
- run-command: report exec failure
A recent update accidentally squelched an error message when the
run_command API failed to run a missing command, which has been
corrected.
* nd/show-gitcomp-compilation-fix (2018-12-12) 1 commit
- parse-options: fix SunCC compiler warning
Portability fix for a recent update to parse-options API.
* js/help-commands-verbose-by-default-fix (2018-12-12) 2 commits
- help -a: handle aliases with long names gracefully
- help.h: fix coding style
"git help -a" did not work well when an overly long alias is
defined, which has been corrected.
* js/mailinfo-format-flowed-fix (2018-12-13) 1 commit
- t4256: mark support files as LF-only
Test portability fix.
next reply other threads:[~2018-12-13 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 6:29 Junio C Hamano [this message]
2018-12-13 12:50 ` Preparing for 2.20.1 brown-paper-bag maintenance release Johannes Schindelin
2018-12-13 14:05 ` Ævar Arnfjörð Bjarmason
2018-12-13 18:08 ` Duy Nguyen
2018-12-13 18:17 ` Duy Nguyen
2018-12-14 2:40 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4lbiey7s.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).