fixed
This commit is contained in:
parent
e3f5bd4ca6
commit
d0e94b4302
2 changed files with 13 additions and 0 deletions
|
@ -63,3 +63,5 @@ Enabling `user.useConfigOnly` should prevent this, making it easier to work with
|
||||||
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
||||||
|
|
||||||
Yes, it's great!
|
Yes, it's great!
|
||||||
|
|
||||||
|
> [[fixed|done]] --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,11 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 2"""
|
||||||
|
date="2023-04-04T19:17:56Z"
|
||||||
|
content="""
|
||||||
|
I've made user.useConfigOnly be honored when set.
|
||||||
|
|
||||||
|
Turns out it was not practical for git-annex init to not set user.name and
|
||||||
|
user.email when that is necessary to get git commit to work. But it now
|
||||||
|
avoids setting those when user.useConfigOnly is set.
|
||||||
|
"""]]
|
Loading…
Reference in a new issue