All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>,
	git-for-windows <git-for-windows@googlegroups.com>,
	git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git for Windows 2.27.0-rc0
Date: Mon, 18 May 2020 05:04:19 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2005180503440.55@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAGyf7-Fkn2uHLCqM-4qfM0YQAXoMgiMwKEaxkGkOtz=pYYKQWg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]

Hi Bryan,

On Sat, 16 May 2020, Bryan Turner wrote:

> On Sat, May 16, 2020 at 7:10 AM Johannes Schindelin <
> Johannes.Schindelin@gmx.de> wrote:
>
> > Hi Bryan,
> >
> > On Fri, 15 May 2020, Bryan Turner wrote:
> >
> > > On Fri, May 15, 2020 at 10:32 AM Johannes Schindelin
> > > <johannes.schindelin@gmx.de> wrote:
> > > >
> > > > Dear Git users,
> > > >
> > > > I hereby announce that Git for Windows 2.27.0-rc0 is available from:
> > > >
> > > >
> > https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc0.windows.1
> > >
> > > I've added the 2.27.0-rc0 release candidates for Git and Git for
> > > Windows to Bitbucket Server's test matrix. No failures to report.
> > >
> > > Thanks as always for these early release candidates!
> >
> > Thank you so much!
> >
> > To be honest, this time round I would _really_ like to ask for some manual
> > testing. I upgraded the MSYS2 runtime from being based on Cygwin v3.0.7 to
> > v3.1.4, and the biggest new feature is support for those new-fangled
> > pseudo terminals that Windows 10 now supports. I did find a couple of
> > rough edges in my use cases, but I am not exactly a typical Git for
> > Windows user...
> >
> > Could I ask for some manual testing in particular of anything run inside
> > the Git Bash?
>
>
> I’m happy to set it up and use it as my daily driver on one of my
> workstations, but I don’t want to overpromise how much help I can really
> offer for that sort of testing. I don’t do much of my full-time development
> on Windows anymore for a variety of reasons, so even if I install it in my
> Windows machines I won’t get that much active use in. And when I do use
> Windows, I keep my workflow pretty simple, so aside from basic adds and
> commits with an occasional checkout or very rare rebase, I just don’t cover
> that much functionality.
>
> Sorry I can’t offer much when it comes to end user style testing, Dscho.

Oh, please don't apologize. I appreciate all your help!

Ciao,
Dscho

  parent reply	other threads:[~2020-05-18 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 17:32 [ANNOUNCE] Git for Windows 2.27.0-rc0 Johannes Schindelin
2020-05-15 21:15 ` Bryan Turner
2020-05-16  8:46   ` Johannes Schindelin
     [not found]     ` <CAGyf7-Fkn2uHLCqM-4qfM0YQAXoMgiMwKEaxkGkOtz=pYYKQWg@mail.gmail.com>
2020-05-18  3:04       ` Johannes Schindelin [this message]
2020-05-19 11:16         ` pseudo terminal support, was Re: [git-for-windows] " Johannes Schindelin
2020-05-20 14:04           ` Đoàn Trần Công Danh
     [not found]       ` <CAO49JtG16UROGn2yYCTrwdQHfSz819_PMfyEit8Gwzh9G6Oyow@mail.gmail.com>
2020-05-18  3:04         ` Johannes Schindelin

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=nycvar.QRO.7.76.6.2005180503440.55@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=bturner@atlassian.com \
    --cc=git-for-windows@googlegroups.com \
    --cc=git-packagers@googlegroups.com \
    --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.