Kevin Ballard <kevin@xxxxxx> writes: > As for dropping this conversation now, I'd love to. If you really want > to drop it, I urge you to do just that - don't respond to this > message. Read it, digest it, and then just let it sit. If this is the > last message on the subject, that would be *wonderful*. But if you > respond to this message then you have absolutely no ground to accuse > me of refusing to drop it. So please, don't. I would not have said that if I were you. That makes you look very bad. The impression I get after reading the above is that the only thing you care about is to have the last word in the thread. People with opinions different from you could tone their message down and stick to a more neutral sounding statement, "This patch works around the issue X on HFS+", but not everybody is always nice-and-calm. But _you_ do not have to counter fire with fire, especially if your goal isn't to flame but is to resolve technical issues with cool head. As long as you do not get upset and start the flamewar every time whenever somebody says "This patch works around the issue only that broken crap HFS+ has due to its stupid filename corruption choice it made", when he could just have said it in a more neutral way, we can keep the conversation constructive and civilized. Let me suggest an alternative, as I think this thread raged on long enough. When you read somebody says "HFS+ corrupts", "HFS+ is broken", "this works around the stupidity of HFS+", just take a deep breath, pretend that you did not hear these words that make you feel insulted. Instead pretend that you heard "HFS+ normalizes", "HFS+ is different", and "fixes problem on HFS+". Do not respond with "No it is not a corruption", "No, HFS+ is not broken" and "No, that is not a work around, but is a fix" with another long thread. I can imagine a civilized conversation to go this way: Linus: This patch would hopefully work around the stupid and broken normalization choice HFS+ people made years ago. You: Ok, I tested that patch, and it does fix the issue for me on HFS+ for most cases, but I still have issues if I use character X, Y and Z. Linus: Yeah, that is another direct consequence of the stupidity of HFS+. At this point I think the previous patch bends git backwards enough and I do not know if it is worth addressing by bending further... You: How about introducing this new structure so that these cases can be handled in a way more friendly to HFS+, like this patch? Linus: Yeah, I can buy that, it looks ugly but it would not hurt people on other systems. Hmm? - 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
