which provides per-remote parallelism. My "fetch --all" times go down
from ~60 seconds to ~5 seconds, which is great!
Signed-off-by: Palmer Dabbelt
---
This is more of an RFC that an actual patch, for three reasons:
* I'm not sure if it's safe to access the .git database from multi
This does not change any functionality, but instead just prepares for
the upcoming "--fetch-jobs=" support. Essentially the "max_children"
variable is ambiguously named, which would complicate the diff in
squashed into the "--fetch-jobs=" patch.
Signed-off-by
It seems like the feedback for v1 was fairly positive, so I managed to
find some time to go ahead finish it. The result is a much cleaner
patch set. I think this could be merged in its current state, but there
are a few outstanding concerns I have:
* fetch.jobs isn't documented because I couldn'
fetched and the result is an
error).
Signed-off-by: Palmer Dabbelt
---
Documentation/fetch-options.txt | 5 ++
builtin/fetch.c | 141 +++-
2 files changed, 126 insertions(+), 20 deletions(-)
diff --git a/Documentation/fetch-options.txt b/Documentatio
This is exactly the same as --jobs, but the more explicit name will
allow us to later change the behavior of --jobs to control both the
number of jobs for remotes as well as submodules.
Signed-off-by: Palmer Dabbelt
---
Documentation/fetch-options.txt | 1 +
builtin/fetch.c | 2
both
max_children_for_{submodules,fetch}, as well as noting this new behavior
in the documentation.
Signed-off-by: Palmer Dabbelt
---
Documentation/fetch-options.txt | 4
builtin/fetch.c | 21 ++---
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git
te any for this one. I've tested this in my config and in
conjunction with the command-line argument.
Signed-off-by: Palmer Dabbelt
---
builtin/fetch.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/builtin/fetch.c b/builtin/fetch.c
index fa12ad44e7d9..4c5f2ea3a931 100644
--- a/b
On Tue, 13 Aug 2019 15:00:13 PDT (-0700), gits...@pobox.com wrote:
Palmer Dabbelt writes:
The existing --jobs argument was defined to control the number of jobs
used for submodule fetching, but it makes more sense to have this
argument control the number of jobs to be used when fetching from
On Tue, 13 Aug 2019 13:16:11 PDT (-0700), johannes.schinde...@gmx.de wrote:
Hi,
On Mon, 12 Aug 2019, Palmer Dabbelt wrote:
The existing --jobs argument was defined to control the number of jobs
used for submodule fetching, but it makes more sense to have this
argument control the number of
On Wed, 14 Aug 2019 01:32:45 PDT (-0700), szeder@gmail.com wrote:
On Mon, Aug 12, 2019 at 02:34:48PM -0700, Palmer Dabbelt wrote:
diff --git a/builtin/fetch.c b/builtin/fetch.c
index 67d001f3f78b..41498e9efb3b 100644
--- a/builtin/fetch.c
+++ b/builtin/fetch.c
@@ -114,6 +114,20 @@ static
On Thu, 12 Sep 2019 11:02:42 PDT (-0700), gits...@pobox.com wrote:
Johannes Schindelin writes:
* pd/fetch-jobs (2019-08-13) 5 commits
. fetch: make --jobs control submodules and remotes
. fetch: add the --submodule-fetch-jobs option
. fetch: add the fetch.jobs config key
. fetch: add the "
On Mon, 16 Sep 2019 10:43:28 PDT (-0700), gits...@pobox.com wrote:
Palmer Dabbelt writes:
... It looks
like there are some test failures when I rebase to the latest master,
which I'm happy to fix. Just let me know if I should:
* Send just the first 4 patches, holding onto the las
12 matches
Mail list logo