Hi Hannes,
I'd like to follow up on your recommendation of using sparse checkout to resolve
that CR-in-directory-name problem.
According to my upstream, they can't change that directory name. It works fine
on all their Mac systems. I'm the first one using the PC system. So I have to
resort to the sparse checkout.
This is what I did:
1. Created a file .git/info/sparse-checkout that contains these lines:
*
!title_add_tags_to.png
!title_tagging.png
The above two files are the only ones that are listed in that problematic
directory name "public/images/tagging\rtagging/".
2. To enable sparsecheckout, modified file .git/config:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
sparsecheckout = true <------- added this line
[remote "origin"]
url = git@xxxxxxxxxx:XXX/YYY.git
fetch = +refs/heads/*:refs/remotes/origin/*
Then I issued the command
$ git checkout -b master origin/master
Checking out files: 100% (937/937), done.
Branch master set up to track remote branch master from origin.
Already on 'master'
Voila, it works. That "tagging\rtagging/" directory was not created in folder
"public/images/".
Thanks.
Hoca
--
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