From: Junio C Hamano <gitster@pobox.com>
To: Victoria Dye <vdye@github.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Derrick Stolee <derrickstolee@github.com>
Subject: Re: Git 2.41 release date
Date: Wed, 22 Mar 2023 12:16:21 -0700 [thread overview]
Message-ID: <xmqq7cv8egvu.fsf@gitster.g> (raw)
In-Reply-To: <f337e514-8d3b-927a-5fe3-34f67f199435@github.com> (Victoria Dye's message of "Wed, 22 Mar 2023 10:59:50 -0700")
Victoria Dye <vdye@github.com> writes:
> While perusing the Git Calendar [1], I noticed that the final 2.41 release
> date is on a major US holiday (Memorial Day, May 29). In the past, release
> dates have been shifted to avoid situations like this, and doing so has been
> noticeably helpful to downstream maintainers/integrators. Would it make
> sense to similarly shift 2.41?
Surely, I will be accomodating, of course. Thanks for spotting.
How does Thu June 1st sound?
next prev parent reply other threads:[~2023-03-22 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 17:59 Git 2.41 release date Victoria Dye
2023-03-22 19:16 ` Junio C Hamano [this message]
2023-03-23 4:27 ` Victoria Dye
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=xmqq7cv8egvu.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=vdye@github.com \
/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 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 NNTP newsgroup(s).