Hello, On Sat 03 Aug 2024 at 05:52pm -04, Nicholas D Steeves wrote:
> That's what you said last time (two or three years ago), and the time > before, and the time before... Dgit also has this tool: > > dgit setup-mergechangelogs > > as well as > > dgit update-vcs-git > > which is even easier to use than what I proposed. Whether due to > carelessness, or contempt of teamwork, making this kind of mess is > unacceptable. When a new contributor does something like this, we > expect them to clean up their mess and to not make extra work for every > member of the team. As a senior member of the team, you know how to be > collaborative; this is part of our CoC. > > You would expect anyone else to clean up their mess and enhance their > scripts, so please clean up your mess and enhance your scripts. I disagree that what I did is unacceptable, in the service of fixing an RC bug. We had to resolve that problem for the sake of our users. In addition, I think it is fine if my d/changelog entries simply never get represented in team git. They don't really matter -- it's like how (true) binNMU changelog entries are ephemeral. I should have said this earlier. I wish we had better tools in this area so that upset could be avoided. -- Sean Whitton
