From 176f65fb8fc46f6ee770e6617c763c06332f80e5 Mon Sep 17 00:00:00 2001
From: "tomi.ollila@7588dbee63d5e035a85167fe207afb49287f9d1a" <tomiollila@web>
Date: Wed, 26 Dec 2018 20:33:36 +0000
Subject: [PATCH 1/2] Added a comment: git config remote.origin.annex-ignore
 true

---
 ...ent_1_98a1986ff2047de981d77755c462b690._comment | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 doc/tips/centralized_git_repository_tutorial/on_GitHub/comment_1_98a1986ff2047de981d77755c462b690._comment

diff --git a/doc/tips/centralized_git_repository_tutorial/on_GitHub/comment_1_98a1986ff2047de981d77755c462b690._comment b/doc/tips/centralized_git_repository_tutorial/on_GitHub/comment_1_98a1986ff2047de981d77755c462b690._comment
new file mode 100644
index 0000000000..6ea1c722fc
--- /dev/null
+++ b/doc/tips/centralized_git_repository_tutorial/on_GitHub/comment_1_98a1986ff2047de981d77755c462b690._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="tomi.ollila@7588dbee63d5e035a85167fe207afb49287f9d1a"
+ nickname="tomi.ollila"
+ avatar="http://cdn.libravatar.org/avatar/a794ec01b038c83c4d568d17dc4ceeab"
+ subject="git config remote.origin.annex-ignore true"
+ date="2018-12-26T20:33:36Z"
+ content="""
+Something like 
+
+    git config remote.origin.annex-ignore true
+
+could be useful information in this page. It took me 1.5 hours to figure this out for me (while coding)...
+
+"""]]

From 81cd3c7d2a81811b6afeb66fdebc374e521070c6 Mon Sep 17 00:00:00 2001
From: "travis.a.everett@3055951666d9c7bb74d8826294a71629368f5b92"
 <travisaeverett@web>
Date: Thu, 27 Dec 2018 19:22:45 +0000
Subject: [PATCH 2/2]

---
 doc/todo/git_repo_tracking___40__not_storage__41__.mdwn | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 doc/todo/git_repo_tracking___40__not_storage__41__.mdwn

diff --git a/doc/todo/git_repo_tracking___40__not_storage__41__.mdwn b/doc/todo/git_repo_tracking___40__not_storage__41__.mdwn
new file mode 100644
index 0000000000..6fad284489
--- /dev/null
+++ b/doc/todo/git_repo_tracking___40__not_storage__41__.mdwn
@@ -0,0 +1,8 @@
+If git-annex tracked some information like the repo's remotes, current checkout hash, whether there are uncommitted modifications, branch states, stash state, etc., it seems like it could treat the repo similar to a URL registered for downloading a key. (I've seen the previous threads and agree git-annex should not "store" the repo). With such tracking, I think git-annex could support compelling workflows for managing code/project directories.
+
+A few possibilities:
+
+- Drop a repo for space if the current commit is available in at least N remotes (and all of the repo state is pushed/clean).
+- Create branches or tags in an annex that collect a set of version-compatible checkouts for related projects. The commit/tag messages provide a natural place for meta-commentary
+- Save and version files that aren't quite junk but don't belong *in* a repo (logs, dumps, backups, editor project/workspace files, notes/to-do lists, build-artifacts, test-coverage/linter stat databases, shell history) alongside the repo, making it easier to have a consistent environment for working on one project across multiple systems.
+- Make separate system-specific "master" branches for the main projects directory on each system, then edit and push changes from any other. For example, prep the projects directory on an infrequently-used laptop from your desktop and push/pull the changes.