From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Git Bug Report: git add --patch > "e" makes keyboard unresponsive
Date: Mon, 17 Mar 2025 15:24:07 -0700 [thread overview]
Message-ID: <xmqqsenb70u0.fsf@gitster.g> (raw)
In-Reply-To: <84c3ccdb-2aaf-9b34-91c5-cf5c27f53dcb@gmx.de> (Johannes Schindelin's message of "Sun, 16 Mar 2025 04:34:36 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> I refused to release on a Friday (absent any good reason) which is why
> this version is scheduled to appear this coming Monday.
Not on-topic for any particular bug, but do you want to probably
coordinate on what day of the week a release is made, perhaps? I've
been trying to stick to the same time-of-the-day we established
earlier for embargoed coordinated releases, which is 1700 UTC - 2600
Asia/Tokyo. But the choice of the day-of-the-week has been more or
less arbitrary picked by me to happen on Fridays for the past few
releases; it seems 2.47 was done on Monday.
Any preferences?
next prev parent reply other threads:[~2025-03-17 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 16:22 Git Bug Report: git add --patch > "e" makes keyboard unresponsive Dan Demp
2024-04-24 21:54 ` brian m. carlson
2024-04-24 22:23 ` Junio C Hamano
2024-04-25 4:13 ` Dan Demp
2024-04-25 4:24 ` Junio C Hamano
2024-04-25 4:15 ` Dan Demp
2025-03-16 3:34 ` Johannes Schindelin
2025-03-17 22:24 ` Junio C Hamano [this message]
2025-03-25 11:23 ` Releasing versions on Fridays, was " Johannes Schindelin
2025-03-25 11:44 ` Junio C Hamano
2025-03-26 7:02 ` Johannes Schindelin
2025-03-26 7:53 ` 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=xmqqsenb70u0.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.