Holger Levsen [11/Feb 12:15pm GMT] wrote:
> yes, its not experimental since a week. Hardly mature enough to be recommended
> for *everyone* (as your patch did) which youself have documented on
> https://wiki.debian.org/tag2upload#Not%20supported
>
> btw, I'd expect this URL (until the hash sign probably :) to be included
> in src:devref! (this URL or another which is the canonical documentation
> for tag2upload.)

How's this, then:

--8<---------------cut here---------------start------------->8---
diff --git a/source/pkgs.rst b/source/pkgs.rst
index 41d0147..02a7696 100644
--- a/source/pkgs.rst
+++ b/source/pkgs.rst
@@ -359,7 +359,13 @@ All of the corresponding architecture-dependent and 
architecture-independent
 binary packages, for all architectures, will be built automatically by
 the build daemons in a controlled and predictable environment
 (see :ref:`wanna-build` for more details).
-However, there are several situations where this is not possible.
+
+For many source-only uploads you can use tag2upload instead, which means that
+you only need to push a signed Git tag to Salsa, instead of generating and
+signing ``.dsc`` and ``.changes`` files yourself.
+See https://wiki.debian.org/tag2upload\ .
+
+There are several situations where a source-only upload is not possible.

 The first upload of a new source package (see :ref:`newpackage`)
 must include binary packages, so that they can be reviewed by the
--8<---------------cut here---------------end--------------->8---

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to