Hello,
On Wed 09 Mar 2022 at 01:08pm +01, Lucas Nussbaum wrote:
> On 08/03/22 at 17:33 -0700, Sean Whitton wrote:
>> Lucas, as I've had a lot to do with these git workflows and have
>> probably done the most work documenting them, I can help with any
>> specific follow-up questions you might have.
>
> Thanks!
>
> So the main question I think I have is:
>
> can we find a middleground where the git workflows don't require staying
> with 1.0? Even if that means switching to 3.0 (quilt) using the
> single-debian-patch approach?
dgit-maint-merge(7) works with single-debian-patch and that's what I
use. But it is not clear to me that there are any advantages at all to
that over 3.0 (quilt) with single-debian-patch? Anyway, the main case
where I myself use 1.0 is the following shell alias:
alias ...="sbuild --dpkg-source-opts='-Zgzip -z1 --format=1.0 -sn'"
This is from dgit-user(7). It's the only reasonable way to say "just
sbuild HEAD, please". One reason to continue to use 1.0 in the archive
is to ensure that a way to say "just sbuild HEAD, please" continues to
be supported, as it's very important to have.
Ian has some cases where something that is representable in git is not
representable using 3.0 (quilt) but is representable using 1.0. I don't
have those cases to hand; Ian, could you summarise, please?
> Also, how would that work with packages that combine direct changes to
> upstream, and quilt for Debian-created patches?
Could you expand? I didn't think this category was one of the ones Russ
and I were talking about.
--
Sean Whitton
