summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-11-05 21:25:36 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-11-05 21:25:36 -0400
commited18ba2ba3688601f02cf7916d5e2b003783eebb (patch)
tree833afabc430d830e793e1a0358858c3b23060f26 /doc
parent70db4ebffa5a66ac97791d6780cb203ad6ac642f (diff)
devblog
Diffstat (limited to 'doc')
-rw-r--r--doc/devblog/day_49__direct_mode_guard_implementation.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/devblog/day_49__direct_mode_guard_implementation.mdwn b/doc/devblog/day_49__direct_mode_guard_implementation.mdwn
new file mode 100644
index 000000000..ebc0dd494
--- /dev/null
+++ b/doc/devblog/day_49__direct_mode_guard_implementation.mdwn
@@ -0,0 +1,14 @@
+Long, long day coding up the direct mode guard today. About 90% of the fun
+is dealing with `receive.denyCurrentBranch` not preventing pushes that
+change the current branch, now that core.bare is set in direct mode.
+My current solution to this involves using a special branch when using
+direct mode, which nothing will ever push to (hopefully). A much nicer
+solution would be to use a `update` hook to deny pushes of the current
+branch -- but there are filesystems where repos cannot have git hooks.
+
+The test suite is falling over, but the `directguard` branch otherwise
+seems usable.
+
+----
+
+Today's work was sponsored by Carlo Matteo Capocasa.