From 7f00b7eaf0877e791194e7dfed5abefbb091ee86 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 9 Dec 2015 15:25:14 -0400 Subject: link/copy pointer files to object content when it's added --- doc/todo/smudge.mdwn | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) (limited to 'doc/todo/smudge.mdwn') diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index 949de27da..373c65561 100644 --- a/doc/todo/smudge.mdwn +++ b/doc/todo/smudge.mdwn @@ -330,17 +330,14 @@ files to be unlocked, while the indirect upgrades don't touch the files. such objects. This parallels how inAnnex checks work for direct mode. * Reconcile staged changes into the associated files database, whenever the database is queried. -* See if the case where this is not used can be optimised. Eg, if the - associated files database doesn't exist at all, we know smudge/clean are - not used, so queries for associated files don't need to open the database - or do reconciliation, but can simply return none. +* See if the case where the associated files database is not used can be + optimised. Eg, if the associated files database doesn't exist at all, + we know smudge/clean are not used, so queries for associated files don't + need to open the database or do reconciliation, but can simply return none. Also, no need for Backend.lookupFile to catKeyFile in this case (when not in direct mode). -* Update pointer files when adding the content of a key to the annex - (ie, `git annex get`). - - Check the associated files database to find associated files for the key. - - Check worktree file to ensure it's still a pointer to the key. - - Hard-link to annex object. + However, beware over-optimisation breaking the assistant or perhaps other + long-lived processes. * Update pointer files when dropping the content of a key. - Check the associated files database to find associated files for the key. - Verify that worktree files are not modified from the annexed object. -- cgit v1.2.3