All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: 2.11.0-rc1 will not be tagged for a few days
Date: Thu, 10 Nov 2016 13:43:47 -0800	[thread overview]
Message-ID: <xmqqoa1n57u4.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqk2cgc95m.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Sun, 06 Nov 2016 18:32:05 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> I'll report back an updated schedule when able.

I pushed some updates out on 'master' today.  Between 'master' and
'pu' on the first-parent history there is a merge 52975d2b1f ("Merge
branch 'ls/macos-update' into jch", 2016-11-10) and that matches
what I expect to be in -rc1 tomorrow (modulo RelNotes and the actual
version tag), unless there is a showstopper regresion reported, in
which case we may want to first look into reverting the whole series
that introduced the regression before considering to pile on fix-up
patches.

http://tinyurl.com/gitCal has been redrawn, with -rc1 scheduled for
tomorrow on 11th, -rc2 on the 17th, and final on the 23rd.

Thanks.

  parent reply	other threads:[~2016-11-10 21:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  2:32 2.11.0-rc1 will not be tagged for a few days Junio C Hamano
2016-11-08  0:40 ` 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqoa1n57u4.fsf@gitster.mtv.corp.google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.