From 32c4d03ad1173aa40022cabf1426ab89541603c3 Mon Sep 17 00:00:00 2001 From: Aaron Jacobs Date: Tue, 19 May 2015 16:02:20 +1000 Subject: [PATCH] Clarify that UnlinkOp applies to directories, too. --- fuseops/ops.go | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/fuseops/ops.go b/fuseops/ops.go index 3296d54..117aae4 100644 --- a/fuseops/ops.go +++ b/fuseops/ops.go @@ -436,15 +436,16 @@ func (o *RmDirOp) toBazilfuseResponse() (bfResp interface{}) { return } -// Unlink a file from its parent. If this brings the inode's link count to -// zero, the inode should be deleted once the kernel sends ForgetInodeOp. It -// may still be referenced before then if a user still has the file open. +// Unlink a file or symlink from its parent. If this brings the inode's link +// count to zero, the inode should be deleted once the kernel sends +// ForgetInodeOp. It may still be referenced before then if a user still has +// the file open. // // Sample implementation in ext2: ext2_unlink (http://goo.gl/hY6r6C) type UnlinkOp struct { commonOp - // The ID of parent directory inode, and the name of the file being removed + // The ID of parent directory inode, and the name of the entry being removed // within it. Parent InodeID Name string