[Pkg-netatalk-devel] More patches to flag as submitted upstream

[Daniel Markstedt]

On Sat, May 27, 2023 at 11:56 AM Jonas Smedegaard <jonas at jones.dk> wrote:
>
> Quoting Daniel Markstedt (2023-05-27 20:00:50)
> > Hi Jonas,
> >
> > I have my gitlab account now and confirmed that I can work on my own forks.
> > Here's the fix. :)
> > https://salsa.debian.org/dmark/netatalk/-/tree/dmark/smoke-test-uam-path
> >
> > Can you please add me as a netatalk project member?
> > The gitlab web UI doesn't seem to allow requesting membership.
>
> You should have full access now.
>
> I use Gitlab only as a git repository - I don't use MRs, but if you want
> to use those then feel free to enable them.
>
> Please continue to keep conversations at the Debian bugtracker - i.e. do
> *not* enable issue tracking at Gitlab and if you or anyone else uses
> code comments then it is your responsibility to mirror those over to the
> Debian bugtracker: I find it more important to use a common tooling in
> Debian than to have most fancy tooling for specific packages.
>
> Hope that makes sense.  If you disagree then please shout out, but
> beware that I am most likely very hard to be persuaded on this one...
>

I think your rules make sense for this use case.
MRs and inline code review comments are handy when having multiple
active contributors working on sweeping code changes.

So I commited that trivial smoke test fix to debian/latest
I assume autopkgtest will run again the next time we tag a package version?