Re: What's cooking in git.git (Oct 2016, #04; Mon, 17)
- From
Lars Schneider <larsxschneider@gmail.com>
- Date
- Oct 18, 2016, 20:27 UTC
- Message-ID
- <9F780406-FC77-4B3E-AEEB-7F6215E6702C@gmail.com>
- In-Reply-To
- <xmqqtwcasj8y.fsf@gitster.mtv.corp.google.com>
Show 25 quoted lines
> 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