diff options
| author |  Alex Riesen <raa.lkml@gmail.com> | 2007-01-04 11:22:47 +0100 |
|---|---|---|
| committer |  Junio C Hamano <junkio@cox.net> | 2007-01-10 14:45:20 -0800 |
| commit | f5184380f08c814535e7bda374e403596eef90a3 (patch) | |
| tree | ebf850c18f995e683eababbc7ea412db921c8438 | |
| parent | Provide better feedback for the untracked only case in status output (diff) | |
| download | tgif-f5184380f08c814535e7bda374e403596eef90a3.tar.xz | |
Speed-up recursive by flushing index only once for all entries
The merge-recursive implementation in C inherited the invariant
that the on-file index file is written out and later read back
after any index operations and writing trees from the original
Python implementation. But it was only because the original
implementation worked at the scripting level.
There is no need to write out the index file after handling
every path.
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| -rw-r--r-- | merge-recursive.c | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/merge-recursive.c b/merge-recursive.c index 87a27e0379..aab4c34588 100644 --- a/merge-recursive.c +++ b/merge-recursive.c @@ -954,8 +954,6 @@ static int process_renames(struct path_list *a_renames, path_list_clear(&a_by_dst, 0); path_list_clear(&b_by_dst, 0); - if (cache_dirty) - flush_cache(); return clean_merge; } @@ -1083,9 +1081,6 @@ static int process_entry(const char *path, struct stage_data *entry, } else die("Fatal merge failure, shouldn't happen."); - if (cache_dirty) - flush_cache(); - return clean_merge; } @@ -1133,6 +1128,8 @@ static int merge_trees(struct tree *head, if (!process_entry(path, e, branch1, branch2)) clean = 0; } + if (cache_dirty) + flush_cache(); path_list_clear(re_merge, 0); path_list_clear(re_head, 0); |