git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Lars Schneider <larsxschneider@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2017, #04; Tue, 13)
Date: Wed, 14 Jun 2017 20:38:30 +0200	[thread overview]
Message-ID: <62a0b06d-fbe4-4f00-14d6-83c97ed220e1@web.de> (raw)
In-Reply-To: <3304FB6C-D9A3-42FD-A047-EF97F50BE258@gmail.com>

On 14.06.17 09:42, Lars Schneider wrote:

> 
>> * 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 wonder if anyone has a few free cycles to review this:
> http://public-inbox.org/git/20170601082203.50397-1-larsxschneider@gmail.com/

It's on my todo-list, may be this weekend or so

  reply	other threads:[~2017-06-14 18:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 21:40 What's cooking in git.git (Jun 2017, #04; Tue, 13) Junio C Hamano
2017-06-14  0:52 ` Jonathan Nieder
2017-06-15 15:54   ` Junio C Hamano
2017-06-14  7:42 ` Lars Schneider
2017-06-14 18:38   ` Torsten Bögershausen [this message]
2017-06-14 10:57 ` rs/strbuf-addftime-zZ, was " Johannes Schindelin
2017-06-14 11:10   ` Jeff King
2017-06-14 19:36     ` René Scharfe
2017-06-14 21:04       ` Johannes Schindelin
2017-06-14 23:03         ` René Scharfe
2017-06-15  5:42           ` Jeff King
2017-06-15  8:46             ` René Scharfe
2017-06-14 18:23   ` 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=62a0b06d-fbe4-4f00-14d6-83c97ed220e1@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).