From 82b28a8487ca7bd26d8b142bb2c109e84f608124 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 Aug 2018 15:10:16 -0400 Subject: [PATCH] devblog --- doc/devblog/day_514__v6_bug_review.mdwn | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/devblog/day_514__v6_bug_review.mdwn diff --git a/doc/devblog/day_514__v6_bug_review.mdwn b/doc/devblog/day_514__v6_bug_review.mdwn new file mode 100644 index 0000000000..b8a00ddd5a --- /dev/null +++ b/doc/devblog/day_514__v6_bug_review.mdwn @@ -0,0 +1,25 @@ +Looked over bugs filed about v6 mode and did some triage and analysis. +[[smudge]] has the details. + +This led to changing what's done by `git add` and `git commit file` when +annex.largefiles is not configured. Rather than behaving like `git annex +add` and always storing the file in the annex, it will store it in the +annex if the old version was annexed, and in git if the old version was +stored in git. This avoids accidental conversions. + +It might make sense to have `git annex add` also do this, even in v5 +repositories, but I want to concentrate on v6 for now, and also don't +think that `git add` and `git annex add` necessarily need to behave +identically in v6 mode. While using `git commit -a` doesn't imply +anything about whether you want the file in git or the annex, +using `git-annex add` seems to imply they you want it in +the annex, unless you've gone out of your way to configure otherwise. + +---- + +Also did some design work on supporting versioned S3 buckets with +`git-annex export`. + +---- + +This work is supported by the NSF-funded DataLad project.