From 9d48f2666d80397cc48dd547d32b1806a18b0499 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 17 Oct 2016 14:17:27 -0400 Subject: [PATCH] comment --- ...ment_1_19da9b33836df34b7d747039e6863586._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/todo/unlock_--read-only/comment_1_19da9b33836df34b7d747039e6863586._comment diff --git a/doc/todo/unlock_--read-only/comment_1_19da9b33836df34b7d747039e6863586._comment b/doc/todo/unlock_--read-only/comment_1_19da9b33836df34b7d747039e6863586._comment new file mode 100644 index 0000000000..6047827eac --- /dev/null +++ b/doc/todo/unlock_--read-only/comment_1_19da9b33836df34b7d747039e6863586._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-10-17T18:09:44Z" + content=""" +The protection offered by a read-only mode is pretty minimal; any program +that writes a file atomically using rename will bypass it. So, as programs +are implemented better, they'll bypass this "protection" more -- not much of +a protection! + +Also, it doesn't make much sense to call this operation "unlock" if it's +intended to not let programs modify the files. +"""]]