All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Mar 2021, #04; Sun, 14)
Date: Mon, 15 Mar 2021 18:40:16 -0700	[thread overview]
Message-ID: <xmqqblbjzxj3.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2103150436260.50@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 15 Mar 2021 04:43:09 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> I do not see this in `master`:
> https://github.com/gitster/git/commit/53204061acbf7a03a6ba050f381e0bf9b01e3a78
> claims that it is in `jch`, `jn/mergetool-hideresolved-is-optional`,
> `next` and `seen`, but not in `master`.
>
>> * tb/pack-revindex-on-disk (2021-02-26) 1 commit
>>   (merged to 'next' on 2021-03-12 at 7aa348d3b3)
>>  + pack-revindex.c: don't close unopened file descriptors
>>
>>  Fix for a topic in 'master'.
>
> The same here, I cannot seem to find it in the `master` branch.

Thanks.  I must have fell asleep before pushing them out, after
running a dry-run push and sending out the What's cooking report.

Git 2.31 has been tagged.  We will hopefully either (1) not see
brown-paper-bag breakages at all, or (2) will see some but can
immediately deal with them, in coming couple of days.  After that,
the 2.32 cycle will gain steam, starting next week.  Let's see.

At work HR has been nagging me to take accumulated vacation time, so
I'll officially be off tomorrow but I'll be available to handle such
brown-paper-bag breakages---after all, there aren't many places to
go spend vacation time in right now X-<

      reply	other threads:[~2021-03-16  1:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  5:51 What's cooking in git.git (Mar 2021, #04; Sun, 14) Junio C Hamano
2021-03-15  3:43 ` Johannes Schindelin
2021-03-16  1:40   ` Junio C Hamano [this message]

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=xmqqblbjzxj3.fsf@gitster.g \
    --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. 
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.