From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2016, #04; Mon, 17)
Date: Tue, 18 Oct 2016 13:27:48 -0700 [thread overview]
Message-ID: <9F780406-FC77-4B3E-AEEB-7F6215E6702C@gmail.com> (raw)
In-Reply-To: <xmqqtwcasj8y.fsf@gitster.mtv.corp.google.com>
> On 17 Oct 2016, at 15:28, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>
> * ls/filter-process (2016-10-17) 14 commits
> - contrib/long-running-filter: add long running filter example
> - convert: add filter.<driver>.process option
> - convert: prepare filter.<driver>.process option
> - convert: make apply_filter() adhere to standard Git error handling
> - pkt-line: add functions to read/write flush terminated packet streams
> - pkt-line: add packet_write_gently()
> - pkt-line: add packet_flush_gently()
> - pkt-line: add packet_write_fmt_gently()
> - pkt-line: extract set_packet_header()
> - pkt-line: rename packet_write() to packet_write_fmt()
> - run-command: add clean_on_exit_handler
> - run-command: move check_pipe() from write_or_die to run_command
> - convert: modernize tests
> - convert: quote filter names in error messages
>
> The smudge/clean filter API expect an external process is spawned
> to filter the contents for each path that has a filter defined. A
> new type of "process" filter API has been added to allow the first
> request to run the filter for a path to spawn a single process, and
> all filtering need is served by this single process for multiple
> paths, reducing the process creation overhead.
Hi Junio,
what do you think about v11? Do you feel the series is becoming mature
enough for `next`?
Thanks,
Lars
next prev parent reply other threads:[~2016-10-18 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 22:28 What's cooking in git.git (Oct 2016, #04; Mon, 17) Junio C Hamano
2016-10-17 22:46 ` Pranit Bauva
2016-10-18 20:27 ` Lars Schneider [this message]
2016-10-18 20:31 ` Junio C Hamano
2016-10-19 7:46 ` Jeff King
2016-10-19 20:28 ` brian m. carlson
2016-10-19 21:21 ` Jeff King
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=9F780406-FC77-4B3E-AEEB-7F6215E6702C@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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