[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Accepted magit 4.5.0-1 (source) into unstable



Hi Sean,

Sean Whitton <spwhitton@spwhitton.name> writes:

> Hello,
>
> Debian FTP Masters [07/Jan  4:19am GMT] wrote:
>> Format: 1.8
>> Date: Tue, 06 Jan 2026 18:38:33 -0800
>> Source: magit
>> Architecture: source
>> Version: 4.5.0-1
>> Distribution: unstable
>> Urgency: medium
>> Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org>
>> Changed-By: Xiyue Deng <manphiz@gmail.com>
>> Changes:
>>  magit (4.5.0-1) unstable; urgency=medium
>>  .
>>    * New upstream release
>>    * Update d/gbp.conf to use pristine-tar + upstream history workflow
>>      - The repo actually has both upstream and pristine-tar branches.  It
>>        is better to keep using them for now.
>
> I'd prefer just using upstream tags.  You can delete the pristine-tar
> and upstream branches.

I thought the existence of pristine-tar branch indicates the workflow.
Personally I prefer the dgit-maint-merge workflow anyway which is also
tag2upload compatible.  I have now updated d/gbp.conf and
d/README.source to refer to the dgit-maint-merge workflow.

I haven't deleted the branches yet, because I'm not sure whether the
previous releases that did use pristine-tar could be broken.  Though I
guess we can always get the correct archives either through previous
.dsc from the archive (or snapshot) or from dgit.  If that is indeed the
case, deleting the branches should be no problem.

-- 
Regards,
Xiyue Deng

Attachment: signature.asc
Description: PGP signature


Reply to: