control: retitle -1 dgit-maint-debrebase(7): 'git debrebase quick' not 'git debrebase' before 'git debpush'
Hello,
On Fri 15 Aug 2025 at 11:31pm +01, Ian Jackson wrote:
> Sean Whitton writes ("Bug#1111233: git-debpush: inconvenient to debrebase
> right before uploading"):
>> For git-debrebase packages this is how I upload:
>>
>> git debrebase
>> dgit push-source
>> git push --follow-tags --no-verify
>>
>> I do a debrebase here specifically to ensure that the commit finalising
>> the changelog appears behind the patch queue. This relies on how 'dgit
>> push-source' knows about git-debrebase, and so knows to restitch.
>
> Maybe you want git-debrebase quick
I think you're right. That's exactly what I want.
>> Therefore, I can't easily replace doing a dgit push with 'git debpush'.
>> It would immediately fail on the unstitched branch.
>>
>> I wonder if git-debpush could learn how to restitch.
>
> Currently git-debpush never makes any commits. This is probably a
> good property for it to continue to have.
>
> If it did start to make commits there would be Consequences. For
> example, what would "dry run" mean? How would you debug/test it as a
> cautious user? What about if there's nowhere for those commits to go
> because you're not on a branch? I bet it would turn out that the
> commits would be wrong somehow. etc. etc.
I agree.
I think, then, what I want to do is incorporate mention of 'git
debrebase quick' into dgit-maint-debrebase(7) when I rework it to
recommend uploading with 'git debpush'.
--
Sean Whitton
signature.asc
Description: PGP signature
