Bug#502923: developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...
On 2008-10-21 11:42, Jari Aalto wrote:
> This does not prevent them from being documented in "Best ractises" for
> future use.
I hope, that we only document "best practices" that are already
widely in use or when most people agree. This is not the case
here. If you find "best practices" in the developers reference
that are not widely in use and are disputed, please file a bug.
Reply to:
- References:
- Bug#502923: developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...
- From: jaalto <jari.aalto@cante.net>
- Bug#502923: developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...
- From: Raphael Hertzog <hertzog@debian.org>
- Bug#502923: developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...
- From: Jari Aalto <jari.aalto@tamk.fi>
- Prev by Date:
Bug#502923: developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...
- Next by Date:
Bug#502923: marked as done (developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...)
- Previous by thread:
Bug#502923: developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...
- Next by thread:
Bug#502923: marked as done (developers-reference: Add new Upstream-* fields for Bts, Upstream-Vcs-Browser, Upstream-Vcs-{Git, Hg, Svn) ...)
- Index(es):