From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2016, #07; Fri, 23)
Date: Tue, 27 Sep 2016 16:11:57 -0700 [thread overview]
Message-ID: <xmqqd1jpkkea.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609242101100.129229@virtualbox> (Johannes Schindelin's message of "Sat, 24 Sep 2016 21:05:32 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> In your previous kitchen status ("What's cooking") you hinted at a
> possible v2.10.1 soon. I have a couple of bugfixes lined up for Git for
> Windows and would like to avoid unnecessarily frequent release
> engineering... Any more concrete ideas on a date for this version?
I scanned RelNotes for 2.11 and identified these topics that we'd
want to have in 'maint'.
bw/pathspec-remove-unused-extern-decl # 1 (6 days ago)
rs/checkout-some-states-are-const # 1 (6 days ago)
rs/strbuf-remove-fix # 1 (6 days ago)
rs/unpack-trees-reduce-file-scope-global # 1 (6 days ago)
mr/vcs-svn-printf-ulong # 1 (6 days ago)
sy/git-gui-i18n-ja # 7 (12 days ago)
jk/fix-remote-curl-url-wo-proto # 1 (12 days ago)
js/git-gui-commit-gpgsign # 2 (12 days ago)
jk/patch-ids-no-merges # 2 (6 days ago)
ew/http-do-not-forget-to-call-curl-multi-remove-handle # 3 (6 days ago)
rs/xdiff-merge-overlapping-hunks-for-W-context # 1 (6 days ago)
ks/perf-build-with-autoconf # 1 (6 days ago)
jt/format-patch-base-info-above-sig # 1 (6 days ago)
jk/rebase-i-drop-ident-check # 1 (6 days ago)
jk/reduce-gc-aggressive-depth # 1 (6 days ago)
et/add-chmod-x # 1 (6 days ago)
tg/add-chmod+x-fix # 7 (24 hours ago)
Most are internal clean-ups that I do not mind leaving out, but I
think we want to have that "add --chmod=+x" fix in. As it hasn't
been enough time passed since the topic was merged to 'master', I'd
say either
(1) 2.10.1 with everything other than the last two in a few days
and 2.10.2 late next week with "add --chmod=+x" fix, or
(2) just a single 2.10.1 with everything late next week.
I can go either way and welcome suggestions. I'd start merging
older topics in the above list to 'maint' soonish, but not today.
Thanks.
next prev parent reply other threads:[~2016-09-27 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 22:56 What's cooking in git.git (Sep 2016, #07; Fri, 23) Junio C Hamano
2016-09-24 19:05 ` Johannes Schindelin
2016-09-26 19:09 ` Junio C Hamano
2016-09-27 23:11 ` Junio C Hamano [this message]
2016-10-04 8:06 ` Johannes Schindelin
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=xmqqd1jpkkea.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).