comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 4 Apr 2023 18:43:33 +0000 (14:43 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 4 Apr 2023 18:43:33 +0000 (14:43 -0400)
doc/bugs/Enabling_useConfigOnly_not_honored/comment_1_4f0e4da06d8c9a9db771e593be1e2608._comment [new file with mode: 0644]

diff --git a/doc/bugs/Enabling_useConfigOnly_not_honored/comment_1_4f0e4da06d8c9a9db771e593be1e2608._comment b/doc/bugs/Enabling_useConfigOnly_not_honored/comment_1_4f0e4da06d8c9a9db771e593be1e2608._comment
new file mode 100644 (file)
index 0000000..6644dd8
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2023-04-04T18:34:32Z"
+ content="""
+Yeah, git-annex goes to considerable trouble to make sure it can convince
+git to commit. This is because, when I didn't do that, I was *inundated*
+with bug reports from users with poorly configured systems where git cannot
+guess a default user.name for various reasons.
+
+I'm willing to support user.useConfigOnly, but only to the extent it
+doesn't make me have to deal with all that again.
+
+And I think it's probably unncessary for git-annex to set user.name and
+user.email in the git config ever. It should be able to temporarily override
+them when it needs to do so.
+"""]]