diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-04-11 12:45:05 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-04-11 12:45:49 -0400 |
| commit | c924542e61607d725fbfa51ffbf88d825b4d3382 (patch) | |
| tree | e76c12eec3942efc2c2ab006d5737822bfb500f4 /doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn | |
| parent | 378f61d0ef5564aab28442f09b2462ce7013ce1b (diff) | |
bup: Properly handle key names with spaces or other things that are not legal git refs.
Continue using the key name as bup ref name, to preserve backwards
compatability, unless it is an illegal git ref. In that case, use a sha256
of the key name instead.
Diffstat (limited to 'doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn')
| -rw-r--r-- | doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn b/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn index ea3407577..f8df1f082 100644 --- a/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn +++ b/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn @@ -48,3 +48,5 @@ I tried to restart my session, in case bup adds my username to a group or someth > A workaround is to switch to the SHA256 backend > (`git annex migrate --backend=SHA256`), which avoids spaces in its keys. > --[[Joey]] + +>> Now fixed in git. [[done]] --[[Joey]] |