git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
	Lars Schneider <larsxschneider@gmail.com>,
	Jeff King <peff@peff.net>
Subject: 2.11.0-rc1 will not be tagged for a few days
Date: Sun, 06 Nov 2016 18:32:05 -0800	[thread overview]
Message-ID: <xmqqk2cgc95m.fsf@gitster.mtv.corp.google.com> (raw)

I regret to report that I won't be able to tag 2.11-rc1 as scheduled
in tinyurl.com/gitCal (I am feverish and my brain is not keeping
track of things correctly) any time soon.  I'll report back an
updated schedule when able.

I'd appreciate that people keep discussing and exchanging patches
that will not be in 2.11 final to give a head-start to topics so
that people can agree on the designs and implementations in the
meantime, but one thing I'd like to see when I come back is somebody
tell me (when asked) what fix-up pathes that are "must to apply, or
there is no point tagging 2.11-rc1 while keeping it broken" are
found on the list.  I am aware of only two right now ("cast enum to
int to work around compiler warning", in Dscho's prepare sequencer
series, and "wc -l may give leading whitespace" fix J6t pointed out
in Lars's filter process series), but it is more than likely that I
am missing a few more.

Thanks.  Going back to bed...

             reply	other threads:[~2016-11-07  2:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  2:32 Junio C Hamano [this message]
2016-11-08  0:40 ` 2.11.0-rc1 will not be tagged for a few days Jeff King
2016-11-08  6:25   ` Johannes Sixt
2016-11-08 21:48     ` Jeff King
2016-11-09  6:29       ` Junio C Hamano
2016-11-09 16:51         ` Jeff King
2016-11-09 23:35           ` Junio C Hamano
2016-11-09 23:40   ` Junio C Hamano
2016-11-10 21:43 ` Junio C Hamano
2016-11-11  0:26   ` Junio C Hamano
2016-11-11 16:13   ` Johannes Schindelin
2016-11-11 17:02     ` Johannes Schindelin
2016-11-11 17:05     ` Lars Schneider
2016-11-11 17:31       ` Lars Schneider
2016-11-11 17:38         ` Lars Schneider
2016-11-11 20:44           ` Johannes Sixt
2016-11-11 20:52             ` Junio C Hamano
2016-11-11 21:07               ` Junio C Hamano
2016-11-11 21:22                 ` Johannes Sixt
2016-11-12 13:33                   ` Lars Schneider
2016-11-11 17:41       ` 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=xmqqk2cgc95m.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=larsxschneider@gmail.com \
    --cc=peff@peff.net \
    /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).