-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git meta merge --no-ff
is very very slow
#691
Comments
it takes about the same time with or without half-open enabled: without half-open module:
with half-open module:
The reason is that it takes seconds to merge is because this repo has >6000 submodules and git-meta process iterate over all submodules twice during the merge. One for simple changes like |
Does it iterate over unchanged modules? If it doesn't already contain the
optimization, it seems like merge ought to skip submodules where the
submodule sha is the same in both meta commits.
…On Thu, Feb 14, 2019 at 7:13 PM shijing ***@***.***> wrote:
it takes about the same time with or without half-open enabled:
without half-open module:
$ time git meta merge 720f26ec535e80aec6ab1392037cf7e86eb984eb --no-ff -m 'merge'
Merging meta-repo commit 720f26ec535e80aec6ab1392037cf7e86eb984eb.
real 0m3.939s
user 0m2.133s
sys 0m0.875s
with half-open module:
$ time git meta merge 720f26ec535e80aec6ab1392037cf7e86eb984eb --no-ff -m 'merge'
Merging meta-repo commits f132442efc3a326188f1c6afc3547a3fc0512a19 and
720f26ec535e80aec6ab1392037cf7e86eb984eb
Merge commit created at 2f876012e0c856430f8cfc8855b49da298a1ddc2.
real 0m2.212s
user 0m1.657s
sys 0m0.599s
The reason is that it takes seconds to merge is because this repo has
>6000 submodules and git-meta process iterate over all submodules twice
during the merge. One for simple changes like adding, renaming or deleting
submodules and the other iteration is for complicated merge conflicts if
there are any.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#691 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAO6IulUQLdn-McHIfQrpNJOxrptvgbyks5vNfuYgaJpZM4a8CtH>
.
|
Repro steps:
Expected:
Actual:
The text was updated successfully, but these errors were encountered: