On 1/25/25 17:13, Bruno Haible via Gnulib discussion list wrote:
But from the perspective of the developer, there's a difference: Why force a shaming term on a developer that makes adaptations?
I don't see it like that. It's not a statement about the code but about the state in the version control system. And I'm fine with "dirty" for this. I would not at all think in the direction of being ashamed, it's just a state. Maybe like dirty plates in a restaurant kitchen: it's something natural that kitchen chefs use plates temporarily and then put them into the dish washer, but - like in software - it's not something one would hand out to a customer: the meal is always prepared on its own fresh plate. I don't see "dirty" as a bad term per se. But I'd leave the word to some native speakers. Have a nice day, Berny
