There is also a case insensitive alternative [section.subsection]
syntax. In this syntax, subsection names follow the same restrictions
as for section names.
If I define [section.SUBSECTION] (aka, not all lowercase), I cannot
use: git config section.SUBSECTION.option, but rather only git config
Hi,
I am new to the GIT world and try to manage a
multiple developers local git repo.
I created a local repo by `git clone --bare`.
Then, I git clone from that local repo to my work area.
After made a change, I committed and pushed back
to the local repo.
At the local repo, `git show commit`
Sorry for confusion. I got my mess sorted out ;)
When I cloned, i was in orign/master. I made a mistake
at checking out the branch I wanted. The branch I actually
checked out was the master branch but under the name I
thought otherwise.
It now worked great!
Cheers,
Jay
Jay Lan wrote:
Hi,
I
