From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailinglist <git@vger.kernel.org>, phillip.wood@dunelm.org.uk
Subject: Re: What's cooking in git.git (Jun 2017, #06; Thu, 22)
Date: Fri, 23 Jun 2017 11:43:41 +0200 [thread overview]
Message-ID: <AEBB93E7-7D91-4D0D-96C9-F2AB1AE079FD@gmail.com> (raw)
In-Reply-To: <xmqqinjnhcr8.fsf@gitster.mtv.corp.google.com>
> On 23 Jun 2017, at 00:35, 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
>
> --------------------------------------------------
>
...
>
> * ls/filter-process-delayed (2017-06-01) 5 commits
> - convert: add "status=delayed" to filter process protocol
> - convert: move multiple file filter error handling to separate function
> - t0021: write "OUT" only on success
> - t0021: make debug log file name configurable
> - t0021: keep filter log files on comparison
>
> The filter-process interface learned to allow a process with long
> latency give a "delayed" response.
>
> Needs review.
I am still desperately looking for reviewers!
It would be awesome if this feature would have a chance
to go into 2.14 :-)
> * pw/rebase-i-regression-fix-tests (2017-06-19) 4 commits
> (merged to 'next' on 2017-06-22 at d1dde1672a)
> + rebase: add more regression tests for console output
> + rebase: add regression tests for console output
> + rebase -i: add test for reflog message
> + sequencer: print autostash messages to stderr
>
> Fix a recent regression to "git rebase -i" and add tests that would
> have caught it and others.
>
> Will merge to 'master'.
I think this series breaks t3420-rebase-autostash.sh
with GETTEXT_POISON=YesPlease
See: https://travis-ci.org/git/git/jobs/245990993
- Lars
next prev parent reply other threads:[~2017-06-23 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 22:35 What's cooking in git.git (Jun 2017, #06; Thu, 22) Junio C Hamano
2017-06-22 22:58 ` Ævar Arnfjörð Bjarmason
2017-06-23 5:28 ` Junio C Hamano
2017-06-24 0:27 ` Junio C Hamano
2017-06-23 9:43 ` Lars Schneider [this message]
2017-06-23 21:59 ` Ævar Arnfjörð Bjarmason
2017-06-23 23:39 ` Stefan Beller
2017-06-24 0:37 ` Junio C Hamano
2017-06-24 1:01 ` Junio C Hamano
2017-06-27 2:58 ` Stefan Beller
2017-06-24 0:16 ` Stefan Beller
2017-06-24 0:33 ` 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=AEBB93E7-7D91-4D0D-96C9-F2AB1AE079FD@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
/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).