Kurt Roeckx <k...@roeckx.be> writes: > As far as I know, the archive maps uploads to testing to > testing-proposed-updates, and so both end up in t-p-u.
Yeah, but t-p-u is the recommended method, IIRC. > There is also testing-security, which first gets uploaded to > security-master.debian.org and then also gets mapped to t-p-u when > uploaded to ftp-master. Those are mentioned briefly in a later paragraph that I didn't quote again. > But I wonder why we need such a list in policy. A few examples might be > useful, but this more looks like something for the developers reference > to me. I agree that devref is canonical. The hard part about listing some examples is that I wasn't sure where to stop; there aren't that many that are really in use. Listing a couple of examples is most of the work of listing the four that we actually use (plus mentioning the security ones). But if people feel it would be better, I can trim the footnote even further. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
