From: Victoria Dye <vdye@github•com>
To: Junio C Hamano <gitster@pobox•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 21:27:19 -0700 [thread overview]
Message-ID: <48664dbe-b777-1019-8941-e2948dd55f53@github.com> (raw)
In-Reply-To: <xmqq7cv8egvu.fsf@gitster.g>
Junio C Hamano wrote:
> 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?
Thank you so much! June 1st sounds great.
prev parent reply other threads:[~2023-03-23 4:28 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
2023-03-23 4:27 ` Victoria Dye [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=48664dbe-b777-1019-8941-e2948dd55f53@github.com \
--to=vdye@github$(echo .)com \
--cc=derrickstolee@github$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=johannes.schindelin@gmx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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