git annex fsck in bare repository
Hi all (i.e. Joey), git annex fsck is a no-op in a bare repository. While I can understand that there is no (easy) way to verify the symlinks, the annex objects are there regardless. Wouldn't it make sense to allow me to check repo integrity in bare repos, as well? As an aside, should those smaller issues go into the wiki or onto this list? Both is fine by me. Personally, I would lean towards Keep small stuff on the list, save in wiki if there is a need. Thanks, Richard ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: git annex fsck in bare repository
Richard Hartmann wrote: Hi all (i.e. Joey), git annex fsck is a no-op in a bare repository. While I can understand that there is no (easy) way to verify the symlinks, the annex objects are there regardless. Wouldn't it make sense to allow me to check repo integrity in bare repos, as well? Yes, fsck could check the size and checksum (if available). It could not check the location log correctness or number of available copies. As an aside, should those smaller issues go into the wiki or onto this list? Both is fine by me. Personally, I would lean towards Keep small stuff on the list, save in wiki if there is a need. I prefer to track such stuff on the wiki. -- see shy jo signature.asc Description: Digital signature ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: git annex fsck in bare repository
On Mon, Jun 13, 2011 at 18:43, Joey Hess j...@kitenet.net wrote: Yes, fsck could check the size and checksum (if available). It could not check the location log correctness or number of available copies. Sounds good to me. I am only concerned about data integrity, anyway. I prefer to track such stuff on the wiki. http://git-annex.branchable.com/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/?updatedRichard Richard ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
