summaryrefslogtreecommitdiff
path: root/doc/design
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-06-12 19:52:57 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-06-12 19:52:57 -0400
commit7e8897c037bff318f7ff57c146023f1e69f3a1ab (patch)
treed265bbab8480ca6a663b57a20aac60eac2084226 /doc/design
parent3033988525b7c0b99e373517d4a1b24dfca440ea (diff)
blog for the day
Diffstat (limited to 'doc/design')
-rw-r--r--doc/design/assistant/blog/day_282-283__caught_up.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_282-283__caught_up.mdwn b/doc/design/assistant/blog/day_282-283__caught_up.mdwn
new file mode 100644
index 000000000..b097e8d24
--- /dev/null
+++ b/doc/design/assistant/blog/day_282-283__caught_up.mdwn
@@ -0,0 +1,18 @@
+Got caught up on my backlog yesterday.
+
+Part of adding files in direct mode involved removing write permission from
+them temporarily. That turned out to cause problems with some programs that
+open a file repeatedly, and was generally against the principle that direct
+mode files are always directly available. Happily, I was able to get rid of
+that without sacrificing any safety.
+
+Improved syncing to bare repositories. Normally syncing pushes to a
+synced/master branch, which is good for non-bare repositories since git
+does not allow pushing to the currently checked out branch. But for bare
+repositories, this could leave them without a master branch, so cloning
+from them wouldn't work. A funny thing is that git does not really have any
+way to tell if a remote repository is bare or not. Anyway, I did put in a
+fix, at the expense of pushing twice (but the git data should only be
+transferred once anyway).
+
+