git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git-for-windows@googlegroups.com, git@vger.kernel.org,
	git-packagers@googlegroups.com
Subject: Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2
Date: Wed, 3 Jun 2020 15:54:03 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2006031550400.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqlfl5rwug.fsf@gitster.c.googlers.com>

Hi Junio,

On Tue, 2 Jun 2020, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> >> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >>
> >> > Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> >> > v2.27.0 is released early enough).
> >>
> >> Thanks for a reminder that Europe is ahead of me by about a bit less
> >> than half a day ;-)
> >
> > You're welcome ;-)
>
> I'll remind myself that I'll try to tag and push out the final
> before 1700 UTC, which would be around 10AM for me ;-)

That will work. That's 7pm for me, which is still safely after-hours, but
it's better than 2am.

On the other hand, I do not even think that Git for Windows versions
_need_ to be released on the same calendar day as Git versions.

For v2.27.0, for example, in hindsight I would have preferred to wait
until the next day so that I could have tested it much more thoroughly.
The symbolic link stuff we were talking about does not work correctly, and
I had missed that because I just "rushed out" a release on what was a
holiday for me.

So while I appreciate your concern, I think you need not bend over all
that much, it is not necessary.

Thank you!
Dscho

  reply	other threads:[~2020-06-03 13:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 20:45 [ANNOUNCE] Git for Windows 2.27.0-rc2 Johannes Schindelin
2020-05-28 21:35 ` symbolic links in Git for Windows v2.27.0, was " Johannes Schindelin
2020-05-29 17:23   ` Junio C Hamano
2020-05-29  5:56     ` Johannes Schindelin
2020-05-29 22:32   ` brian m. carlson
2020-05-29 13:40     ` Johannes Schindelin
2020-05-30 16:49       ` brian m. carlson
2020-05-30  8:03         ` Johannes Schindelin
2020-06-01 21:05   ` Junio C Hamano
2020-06-02 20:32     ` Johannes Schindelin
2020-06-02 21:17       ` Junio C Hamano
2020-06-03 13:54         ` Johannes Schindelin [this message]
2020-06-03 19:34           ` 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.2006031550400.56@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).