diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2011-10-25 21:40:30 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-10-25 21:40:30 +0000 |
| commit | 12a0a45fb1ddb464d7863cdd707dd4b328ae5df5 (patch) | |
| tree | 8c3d7cc69c671e0478a968b36cf307788d5d26a0 /doc/todo | |
| parent | 570aae9bbcdd6a7d5972288d322da3872d0a17be (diff) | |
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/support_fsck_in_bare_repos.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/todo/support_fsck_in_bare_repos.mdwn b/doc/todo/support_fsck_in_bare_repos.mdwn new file mode 100644 index 000000000..b126a8170 --- /dev/null +++ b/doc/todo/support_fsck_in_bare_repos.mdwn @@ -0,0 +1,10 @@ +What is says on the tin: + + + 22:56:54 < RichiH> joeyh_: by the way, i have been thinking about fsck on bare repos + 22:57:37 < RichiH> joeyh_: the best i could come with is to have a bare and a non-bare access the same repo store + 22:58:00 < RichiH> joeyh_: alternatively, with the SHA* backend, you have all the information to verify that the local data is correct + 22:58:41 < RichiH> and verifying that would already be a plus. if there really _is_ a problem, having the SHA is enough to track issues down + 23:09:50 < joeyh_> oh, I think I have code that fsck could use on bare repos already.. just a matter of wiring it up + 23:10:42 < joeyh_> feel free to reopen a bug or whatever so I remember.. the unused command's branch content enumeration could be used in a bare repo + 23:14:51 < joeyh_> unused/dropunused could work in bare repos too btw |