On Tue, 25 Jun 2024 at 10:02:03 +0200, Thomas Goirand wrote:
> I do not think it is reasonable that a particular (git?) workflow, specific
> to the way *YOU* prefer working, gains special upload rights.
This seems to be based on a misconception. tag2upload specifically
doesn't require one specific git workflow! It supports several common git
workflows, including "manage the patches in debian/patches using quilt".
> I've read
> about the deb-rebase workflow, I would hate it, and prefer managing patches
> with quilt directly.
For what it's worth, I also prefer a "patches unapplied" workflow
equivalent to the one used in pkg-perl, pkg-gnome and similar teams.
I use gbp-pq rather than quilt, but the principle is the same, and they
interoperate with each other - I can use gbp-pq for the same source package
and git repo where my GNOME team colleagues use quilt, and it isn't a
problem.
> Does this mean your tag2upload doesn't work for me?
No, tag2upload does not require you to use git-debrebase. git-debrebase
is one of several workflows that it supports. Using quilt or gbp-pq
is another.
I believe tag2upload supports all of the source tree layouts that dgit
does, and I regularly upload gbp-pq-based packages with `dgit push-source`,
which works fine.
smcv
