Stefan Beller <sbel...@google.com> writes:
> Where does it apply?
> ---
> This applies on 376d400f4c (run-command: fix missing output from late
> callbacks,
> which is the latest commit in origin/sb/submodule-parallel-fetch which was
> merged to origin/next)
Thanks for a detailed description. I'd do this:
$ git checkout -b sb/submodule-parallel-update 8b70042
$ git merge sb/submodule-parallel-fetch~4 ;# 376d400f4c
apply 2-9 there (the fork point is the merge of config-parse topic
to 'master'), and drop the four patches near the top of the other
branch.
> I realize sending refactorings in the area you'd be likely to touch as
> a separate patch (series) is not necessarily a good idea as it leads to
> situations like this.
Don't worry too much about it. When you tackle a large area with a
lot of existing code, these things are bound to happen.
> What does it do?
> ---
> This series should finish the on going efforts of parallelizing
> submodule network traffic. The patches contain tests for clone,
> fetch and submodule update to use the actual parallelism both via
> command line as well as a configured option.
;-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
