Windows case-sensitivity detection - partly fixed

DeeJay smartgpx at gmail.com
Tue Dec 4 13:40:04 GMT 2007


On 29th Nov, in response to a suggestion that this issue had
no bug report despite knowing I had submitted one, I wrote - perhaps
a trifle brusquely -

"The fact that it is possible to perform a commit which effectively
renders the branch incapable of being transformed back into a
working tree on the same machine seems such a fundamental
failing that I have been looking at alternative DVCS's. If you give
me my repository back I'll come back home to bzr."

I am pleased to see that in part this has been fixed in 1.0rc1, to
the extent that I can now 'branch' or 'pull' the corrupted branch
and get back a versioned working tree (albeit with one of the
files 'renamed' out of the way - a reasonable compromise, and
superior to the misleading report about .bzr/checkout/limbo that
was in 0.91.)

More work needs to be done on detecting and preventing the
corruption in the first place - new bug reports have been lodged on
those topics, and discussion on how to deal with them has followed.

So, if you'll have me, I'm back on board as a one-man-band user
of Bazaar on Windows. But not uncritically.

I've been making suggestions to Ian for making the documentation
he is working on 'Windows-friendly'. Overall, it still seems to me
that Windows is a bit of a second-class citizen: for instance, much
of the documentation does not acknowledge Windows, and we seem
to be reliant on one volunteer [to whom many thanks] for packaging
the Windows installer. And if I encounter a problem I don't want to
be told to use another OS! Do the core Bazaar developers, testers,
documentors and maintainers have access to a Windows system
to reinforce their efforts? If not, should they have?

Best wishes for the push to v1.0

DJ
Leicester, UK



More information about the bazaar mailing list