From: Junio C Hamano <gitster@pobox.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Git List <git@vger.kernel.org>, Taylor Blau <ttaylorr@github.com>
Subject: Re: What's cooking in git.git (Dec 2017, #03; Wed, 13)
Date: Tue, 09 Jan 2018 10:59:48 -0800 [thread overview]
Message-ID: <xmqqmv1m6eor.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <ABE531C2-3173-441D-8710-B9B75C97B4F5@gmail.com> (Lars Schneider's message of "Tue, 9 Jan 2018 13:59:43 +0100")
Lars Schneider <larsxschneider@gmail.com> writes:
>> On 14 Dec 2017, at 00:00, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Here are the topics that have been cooking. Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'next'. The ones marked with '.' do not appear in any of
>> the integration branches, but I am still holding onto them.
>>
>> You can find the changes described here in the integration branches
>> of the repositories listed at
>>
>> http://git-blame.blogspot.com/p/git-public-repositories.html
>> ...
>>
>> * jk/progress-delay-fix (2017-12-04) 2 commits
>> (merged to 'next' on 2017-12-05 at 8e62c2b18b)
>> + progress: drop delay-threshold code
>> + progress: set default delay threshold to 100%, not 0%
>>
>> A regression in the progress eye-candy was fixed.
>
> Hi Junio,
>
> this fixes a bug that affects the Git LFS community (not only
> eye-candy). Would it be possible to get this into Git 2.15.2?
The topic is in 'master' and is a candidate to eventually hit the
'maint' track. I do not know if 2.15.2 is warranted, though, as we
are getting closer to 2.16 and supposed to be concentrating more on
regression fixes.
Thanks.
prev parent reply other threads:[~2018-01-09 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:00 What's cooking in git.git (Dec 2017, #03; Wed, 13) Junio C Hamano
2017-12-14 12:37 ` Kaartic Sivaraam
2017-12-14 17:20 ` Junio C Hamano
2017-12-14 21:08 ` Junio C Hamano
2017-12-16 6:06 ` Kaartic Sivaraam
2017-12-14 21:09 ` [PATCH v4 2/3] rebase: distinguish user input by quoting it Junio C Hamano
2017-12-14 21:09 ` [PATCH v4 3/3] rebase: rebasing can also be done when HEAD is detached Junio C Hamano
2017-12-15 15:29 ` What's cooking in git.git (Dec 2017, #03; Wed, 13) Kaartic Sivaraam
2017-12-14 17:41 ` Ævar Arnfjörð Bjarmason
2017-12-14 21:04 ` Jonathan Nieder
2017-12-14 21:06 ` Junio C Hamano
2017-12-14 21:26 ` Jonathan Nieder
2017-12-15 12:39 ` Johannes Schindelin
2018-01-09 12:59 ` Lars Schneider
2018-01-09 18:59 ` Junio C Hamano [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
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=xmqqmv1m6eor.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=ttaylorr@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.
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).