From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>,
git-for-windows <git-for-windows@googlegroups.com>,
Johannes Sixt <j6t@kdbg.org>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [git-for-windows] Git for Windows v2.15.0-rc prerelease, was Re: [ANNOUNCE] Git v2.15.0-rc2
Date: Sat, 28 Oct 2017 18:40:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1710281838230.6482@virtualbox> (raw)
In-Reply-To: <DC84FB2E-A26E-4957-B5FA-BE6DDEC3411B@gmail.com>
Hi Lars,
On Fri, 27 Oct 2017, Lars Schneider wrote:
> > On 27 Oct 2017, at 14:11, Lars Schneider <larsxschneider@gmail.com> wrote:
> >
> >> On 21 Oct 2017, at 00:22, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> >>
> >> [cutting linux-kernel]
> >>
> >> On Fri, 20 Oct 2017, Junio C Hamano wrote:
> >>
> >>> A release candidate Git v2.15.0-rc2 is now available for testing
> >>> at the usual places.
> >>
> >> The Git for Windows equivalent is now available from
> >>
> >> https://github.com/git-for-windows/git/releases/tag/v2.15.0-rc2.windows.1
> >
> > I just tested RC2 on Windows and I don't see my "Filtering content:"
> > output if I clone a Git repository with Git LFS files (and Git LFS
> > 2.3.3+ installed).
> >
> > The feature was introduced in the following commit which is be part of
> > your RC2 build commit (b7f8941):
> > https://github.com/git/git/commit/52f1d62eb44faf569edca360ec9af9ddd4045fe0
> >
> > On macOS everything works as expcted with RC2:
> > ...
> > remote: Total 15012 (delta 0), reused 0 (delta 0), pack-reused 15012
> > Receiving objects: 100% (15012/15012), 2.02 MiB | 753.00 KiB/s, done.
> > Filtering content: 43% (6468/15000), 33.30 KiB | 0 bytes/s
> > ...
> >
> > Do you, or other Windows experts, spot something in the commit linked
> > above that could cause trouble on Windows?
>
> Well, it turns out the output works for my real life repos but not for
> my Git LFS testing repo.
>
> git clone https://github.com/larsxschneider/lfstest-manyfiles
>
> ... prints the filtering content output on macOS but not on Windows.
> The progress function has some delay feature that suppresses the output
> if it is only shown for a second or something. However, in this test case
> the output should be visible for several seconds at least...
> I am still puzzled.
Nothing really strikes me as obvious.
Do you do this in Git Bash? If so, maybe you can also test in Git CMD? I
do remember having issues with stderr only showing up in time if it was
fflush()ed explicitly, but only in Git Bash (i.e. a MinTTY problem).
Ciao,
Dscho
next prev parent reply other threads:[~2017-10-28 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 6:49 [ANNOUNCE] Git v2.15.0-rc2 Junio C Hamano
2017-10-20 22:22 ` Git for Windows v2.15.0-rc prerelease, was " Johannes Schindelin
2017-10-20 23:49 ` Bryan Turner
2017-10-21 2:07 ` Junio C Hamano
2017-10-23 9:42 ` Johannes Schindelin
2017-10-27 12:11 ` [git-for-windows] " Lars Schneider
2017-10-27 12:24 ` Lars Schneider
2017-10-28 16:40 ` Johannes Schindelin [this message]
2017-10-28 16:56 ` Lars Schneider
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=alpine.DEB.2.21.1.1710281838230.6482@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jrnieder@gmail.com \
--cc=larsxschneider@gmail.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).