Sean Whitton <spwhit...@spwhitton.name> writes:

> Nicholas D Steeves <s...@debian.org> writes:
>> Sean Whitton <spwhit...@spwhitton.name> writes:
>>> Hello,
>>>
>>> I am about to do no-change uploads of every addon package to rebuild
>>> them against dh-elpa 2.1.3.
>>>
>>> I will do this using 'dgit clone' and then 'dgit push-source'.
>>> This is because I don't think it's appropriate for me to include changes
>>> that happen to be pushed to salsa, but not uploaded.
>>>
>>> When you next upload any package, please pull in my d/changelog entry.
>>> 'dgit pull' for a patches-applied workflow or there are no patches, else
>>> you'll need to manually merge it in; feel free to ask me for help.
>>
> On Fri 02 Aug 2024 at 07:52pm -04, Nicholas D Steeves wrote:
>
>> Please add this to your script, and create a list of packages that
>> require manual action.  I'm not even asking to enable the changelog
>> merge driver, which could hypothetically make mistakes, and thus
>> increase your workload.  Just please do the bare minimum (add remote,
>> pull, and push) and create a list that requires further action.
>
> I see what you mean.  I'll consider that next time, thanks.

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.

Regards,
Nicholas

Attachment: signature.asc
Description: PGP signature

Reply via email to