git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2015, #06; Wed, 23)
Date: Thu, 24 Sep 2015 11:28:34 +0200	[thread overview]
Message-ID: <0ddd415aa3fdb36def9f7c4c43735afd@dscho.org> (raw)
In-Reply-To: <xmqq8u7wwxql.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On 2015-09-24 00:56, Junio C Hamano wrote:
 
> * jc/fsck-dropped-errors (2015-09-23) 1 commit
>  - fsck: exit with non-zero when problems are found
> 
>  There were some classes of errors that "git fsck" diagnosed to its
>  standard error that did not cause it to exit with non-zero status.

Thanks for this!

> * sb/submodule-parallel-fetch (2015-09-23) 9 commits
>  - submodules: allow parallel fetching, add tests and documentation
>  - fetch_populated_submodules: use new parallel job processing
>  - SQUASH???
>  - run-command: add an asynchronous parallel child processor
>  - run-command: factor out return value computation
>  - strbuf: add strbuf_read_once to read without blocking
>  - xread_nonblock: add functionality to read from fds without blocking
>  - xread: poll on non blocking fds
>  - submodule.c: write "Fetching submodule <foo>" to stderr
>  (this branch uses sb/submodule-helper.)
> 
>  Add a framework to spawn a group of processes in parallel, and use
>  it to run "git fetch --recurse-submodules" in parallel.
> 
>  It seems that the fundamentals are almost there, modulo polishing
>  the overall structure to ensure that future enhancement can be made
>  cleanly.

Awesome. As I stated before, I am a big fan of this enhancement, even if I am sad that I have too little time to participate effectively.
 
Ciao,
Dscho

      reply	other threads:[~2015-09-24  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 22:56 What's cooking in git.git (Sep 2015, #06; Wed, 23) Junio C Hamano
2015-09-24  9:28 ` Johannes Schindelin [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ddd415aa3fdb36def9f7c4c43735afd@dscho.org \
    --to=johannes.schindelin@gmx.de \
    --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;
as well as URLs for NNTP newsgroup(s).