From 7353aa5e7aad3cea8bff556770ff6f301b1978df Mon Sep 17 00:00:00 2001
From: 
 "https://www.google.com/accounts/o8/id?id=AItOawkxmke7K8gEXleVRuQvCK5LHPLIzQA6s0E"
 <Michael@web>
Date: Tue, 11 Jun 2013 20:34:13 +0000
Subject: [PATCH]

---
 doc/forum/Overwriting_data_without_getting_it.mdwn | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 doc/forum/Overwriting_data_without_getting_it.mdwn

diff --git a/doc/forum/Overwriting_data_without_getting_it.mdwn b/doc/forum/Overwriting_data_without_getting_it.mdwn
new file mode 100644
index 0000000000..65ade06b34
--- /dev/null
+++ b/doc/forum/Overwriting_data_without_getting_it.mdwn
@@ -0,0 +1,3 @@
+My collaborators and I use git annex to track various large data files (among some smaller metadata files managed by ordinary git).  Some of these data files need to change completely -- the old ones were just wrong.  So I do a git checkout, but don't `git annex get` because it would just be a waste of time and bandwidth.  This means that my "data files" are just broken symlinks.  Now, I find that by making the necessary directories under `.git/annex/objects/`, I can write to these files in the usual directory structure (not through `.git/annex/objects`).  But now they are are longer symlinks, and git/git-annex doesn't seem to realize that anything has changed.  Is this recoverable?
+
+Would it have been better to just `git rm` (or something) the original version of the file, commit that, and then add the new data?  And if so, how should I go about this now that I've created these many very large files?  If not, what would be the preferred way to do this?