Hello,
# Script to illustrate the problem:
rm -f Config
cat <<\EOF >Config
[Example]
Boolean
Other = yes
EOF
git_Config() { git config --file Config "$@"; }
git version
git_Config --get-regexp '.*\.Boolean' #1. ✓ Ok: example.boolean
git_Config --bool --get-regexp '.*\.Boolean' #2. ✗ NO: example.booleantrue
git_Config --get-regexp '.*\.Other' #3. ✓ Ok: example.other yes
git_Config --bool --get-regexp '.*\.Other' #4. ✓ Ok: example.other true
exit
# Output:
git version 1.7.6.1
example.boolean
example.booleantrue
example.other yes
example.other true
Case 2 omits the space between the key-name and (generated) value,
making the output difficult to parse/process. Without checking,
I assume --int (and friends) have a similar bug?
cheers!
-blf-
--
Brian FOSTER
Principal MTS, Software
Maxim Integrated Products (Microcontroller BU), formerly Innova Card
Web : http://www.maxim-ic.com/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html