Should I see a typechange from git status
when using direct mode = false?
I'm using digiKam to manage photos in a git-annex repository. digiKam will only write XMP sidecar files for real files, not symlinks, so I need to unlock every file in order to sync metadata to XMP files.
Is it possible to suppress typechange in some way?
Thanks.
On branch master
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
typechange: photographers/jboxman/2004/06/16/20040616-004528.jpg
.......
typechange: photographers/jboxman/2004/06/17/20040617-010127.jpg
[annex]
uuid = 56e0d203-7898-xxxx-xxxx-1b04cec6597c
version = 5
largefiles = largerthan=20kb and not (include=*.xmp or include=*.thor or include=bin/*)
direct = false
git-annex version: 6.20171124
build flags: Assistant Webapp Pairing Testsuite S3(multipartupload)(storageclasses) WebDAV FsEvents TorrentParser MagicMime Feeds Quvi
dependency versions: aws-0.17.1 bloomfilter-2.0.1.0 cryptonite-0.24 DAV-1.3.1 feed-1.0.0.0 ghc-8.2.2 http-client-0.5.7.1 persistent-sqlite-2.6.3.1torrent-10000.1.1 uuid-1.3.13 yesod-1.4.5
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384ESHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
local repository version: 5
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
operating system: darwin x86_64
This all seems very OK and expected to me.
When you do
git-annex unlock photographers/jboxman/2004/06/16/20040616-004528.jpg
you are changing out the symlink for the actual file, so git has recognized the thing with this name is different. If you dogit-annex add photographers/jboxman/2004/06/16/20040616-004528.jpg
git-annex will recognize that you have not modified any content and will replace the file with the symlink, the file will no longer appear in git status and the file won't have any commits associated with it.So if you unlock everything, launch digiKam and generate your sidecars, then we see both jpgs and xmps in
git status
. If you then rungit annex add .
all your jpgs will turn back into symlinks and all your xmp files will appear ingit status
per yourlargefiles
rule staged for committing.I haven't tested with your exact setup so I would recommend testing the workflow on a small folder to start.
I don't believe the
git
team has provided any way forgit annex
to hook into thestatus
command to provide different information.You can always do
git annex status
if you want to know whatgit annex
thinks about the current situation.