From 974a78bef10c3046e40400199c3d469aa3946eac Mon Sep 17 00:00:00 2001 From: Cletip Date: Wed, 25 Jun 2025 22:12:57 +0000 Subject: [PATCH] =?UTF-8?q?Added=20a=20comment:=20We=20don=E2=80=99t=20nee?= =?UTF-8?q?d=20a=20'git=20annex=20lock'=20after=20a=20'git=20annex=20add',?= =?UTF-8?q?=20right=3F?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ..._201fdec69ebe9fe1afa24e742e3a7dac._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/git-annex-unlock/comment_12_201fdec69ebe9fe1afa24e742e3a7dac._comment diff --git a/doc/git-annex-unlock/comment_12_201fdec69ebe9fe1afa24e742e3a7dac._comment b/doc/git-annex-unlock/comment_12_201fdec69ebe9fe1afa24e742e3a7dac._comment new file mode 100644 index 0000000000..ceae23686f --- /dev/null +++ b/doc/git-annex-unlock/comment_12_201fdec69ebe9fe1afa24e742e3a7dac._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="Cletip" + avatar="http://cdn.libravatar.org/avatar/246315cf8f80f70f9b400c24df275806" + subject="We don’t need a 'git annex lock' after a 'git annex add', right?" + date="2025-06-25T22:12:57Z" + content=""" +Hi there! + +I'm learning how to use `unlock`, and I'm relatively new to `git-annex`. + +I think I’ve understood the concept behind this feature, but I don’t get why, in the example, the `git annex lock` command is used after `git annex add`: + +```bash +git annex unlock photo.jpg +gimp photo.jpg +git annex add photo.jpg +git annex lock photo.jpg <------ This one +git commit -m \"redeye removal\" +``` + +Isn’t the file already locked by the `git annex add` ? + +Thank you in advance. +"""]]