On 2020-03-07 08:00, Andreas Tille wrote: > So well, probably things are there - but that's a confusing branch > layout.
Isn't that DEP-14 branch layout more or less? > Per Debian Science policy branch upstream (missing here) > contains the upstream source and branch master contains the Debian > packaging. Oops, I missed that. Yes, the name should be "debian" or "master" by team policy, not "debian/master". I wonder, whether science team should adopt DEP-14 layout instead? > Since master is the default branch I never looked for > debian/master. Salsa tells me, that debian/master were the default branch. Also, when I "git clone" the repo, I'm automatically in debian/master. Did you do something different maybe? > Its actually not "my fix" I simply realised long term unmerged merge > requests[1], merged them and ended up with a strange repository. Please > feel to fix it - you know I'm not an English speaker either. Yes, we are both native Denglisch speakers :-) > I'd like to hear your opinion about Merge requests in Debian Science > packages. These do not seem to be very popular and thus the work of new > contributors is bit-rotting in Salsa which is sad. I have to confess, that I never look much into Salsa, for none of my packages. How would I know, that there were merge requests? Shouldn't there be bug reports tagged "patch"? Cheers
