(this bug report is a result of a question discussion in IANs tag2upload
talk at the cambridge miniconf 2023)

In the talk Ian made the following points

* the current Salsa approach leads to users accidentlly receiving
patches unapplied git trees
* In a later slide git.dgit.debian.org was identified as a "canonical
git repo" where users could
    obtain the "patches applied" trees that correspond to the archive
contents.
* It was also stated (and is already the case with dgit) that
git.dgit.debian.org would store
    both the maintainers original git tag (which may or may not be
patches applied, but usually
    is not), and the "patches applied" tag that corresponds to the
archive content.

The problem is when a user visits git.dgit.debian.org they just meet a
generic git web
interface with a list of branches, tags etc. It is not at all clear to a
user what each
tag means and in particular what the difference between debian/<version> and
archive/debian/<version> are (IIRC one is the maintainer tree and one is the
"standardised" tree but it's not at all obvious which is which)