| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| |
| | |
* 'add_verify_command' of github:jmurty/git-fat:
Add `verify` command to check git-fat object data matches hash filename.
Conflicts:
git-fat
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While experimenting with using the --partial option with rsync I
managed to corrupt one of my git-fat objects by truncating it. This
caused some behaviour in git-fat which seemed odd until I worked out
what had happened: it would check out the truncated data but git would
see the file as modified and show the changed hash in a diff, while a
re-checkout did not reset the file to its original data/hash.
This commit adds a `verify` command that cross-checks git-fat object
file names (the original SHA1) against the SHA1 of the object's
actual data and prints any mismatches. So you can quickly find any
dubious objects and decide what to do about them.
A better solution might be to calcuate and verify objects' data hash
during filter-smudge/checkout though this would likely hurt performance.
|
| | |
| |
| |
| |
| |
| | |
Since `checkout` op is where the repo really needs to be init'ed for git-fat
I moved the requirement to there. This way it is still triggered by a `pull`
op, but only at the end after any files have been synced.
|
| |/
|
|
| |
This fixes issue #25 in the original project.
|
| |
|
|
| |
If there is any manually removed, tracked file in the working copy, then
running “git fat pull” fails with an OSError without this fix.
|
| |
|
|
|
| |
if a symlink has a length of self.magiclen git-fat would crash
because it could not read the file
|
| | |
|
| | |
|
| | |
|
| |
|
