Added a comment
This commit is contained in:
parent
1a69bf2db7
commit
4515fae064
1 changed files with 14 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="http://joeyh.name/"
|
||||||
|
ip="209.250.56.246"
|
||||||
|
subject="comment 4"
|
||||||
|
date="2013-11-15T17:52:38Z"
|
||||||
|
content="""
|
||||||
|
Looking back at the original bug description:
|
||||||
|
|
||||||
|
\"repo A a symlink to a file whose contents aren't yet available, are overwritten, while at repo B the file is deleted.\"
|
||||||
|
|
||||||
|
I think the \"overwritten\" is key. I suspect you were always doing echo > f where f was a symlink, and this does not actually overwrite the symlink, it just puts data (that fsck will reject) into the annex.
|
||||||
|
|
||||||
|
So, proceeding as if the real bug here is the ability to write through symlink in direct mode, unless told otherwise..
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue