From 8668ca25dce6d712f883221883bf60e382545537 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14" Date: Mon, 16 Feb 2015 20:08:47 +0100 Subject: update for rename of open_issues/git_duplicated_content.mdwn to service_solahart_jakarta_selatan__082122541663/git_duplicated_content.mdwn --- service_solahart_jakarta_selatan__082122541663/git-core-2.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'service_solahart_jakarta_selatan__082122541663') diff --git a/service_solahart_jakarta_selatan__082122541663/git-core-2.mdwn b/service_solahart_jakarta_selatan__082122541663/git-core-2.mdwn index a92b3ebb..ec3a72c9 100644 --- a/service_solahart_jakarta_selatan__082122541663/git-core-2.mdwn +++ b/service_solahart_jakarta_selatan__082122541663/git-core-2.mdwn @@ -277,7 +277,7 @@ Again: warning: unable to unlink ld/testsuite/ld-powerpc: Operation not permitted fatal: cannot create directory at 'ld/testsuite/ld-powerpc': Operation not permitted -And: [[git_duplicated_content]]. +And: [[service_solahart_jakarta_selatan__082122541663/git_duplicated_content]]. All these (very likely) have the same root cause: `SA_RESTART` restarting too much. @@ -289,7 +289,7 @@ invoked every second via `setitimer(ITIMER_REAL)`) to display status messages: To avoid the status update signals every second, in `[git]/progress.c:start_progress_delay` we can just return `NULL` (manually in GDB, for example), then both the *error: git checkout-index* and the -[[duplicated content|git_duplicated_content]] issues go away. +[[duplicated content|service_solahart_jakarta_selatan__082122541663/git_duplicated_content]] issues go away. I'm guessing that when returning from a `SA_RESTART` signal handler, too much of the \`\`syscall''s is being restarted. For example, if a file has already -- cgit v1.2.3