My repo has a change where a directory named Src was renamed to src.
When I run "git filter-branch HEAD", my repo history is rewritten so
it appears that the Src directory was simply deleted. I'm using case
insensitive HFS+.
Fortunately, I can work around this by using -d to work off a case
sensitive HFS+ volume - "git filter-branch -d /Volumes/CaseSensitive/
test HEAD" correctly changes nothing.
Anyone know why this happens?
Jon
Hi,
On Wed, 10 Oct 2007, Jonathan del Strother wrote:
My repo has a change where a directory named Src was renamed to src.
That is no problem for git-filter-branch.
I'm using case insensitive HFS+.
That is the problem.
Of course, we could work around that in git, but frankly, you will turn
into problems once you have files whose names differ only in case. And I
am certain somebody will come soon and report this as a bug in git!
I vote for wont-fix (or more accurately "invalid") in git and
please-fix-in-your-setup.
Ciao,
Dscho
On 10 Oct 2007, at 14:39, Johannes Schindelin wrote:
On Wed, 10 Oct 2007, Jonathan del Strother wrote:
quoted
My repo has a change where a directory named Src was renamed to src.
That is no problem for git-filter-branch.
quoted
I'm using case insensitive HFS+.
That is the problem.
...
I vote for wont-fix (or more accurately "invalid") in git and
please-fix-in-your-setup.
Would love to switch to case sensitive HFS+, but it causes a number of
problems for OS X users - a number of 3rd party applications don't
bother supporting case sensitive formatting (notably Adobe :/ ).
I appreciate that it's difficult and/or impossible to make certain
operations work on case insensitive FS's, but it seems like git ought
to at least complain noisily when it encounters such a situation...