[Piuparts-commits] [piuparts] 01/02: Link https://piuparts.debian.org/bug_howto.html in CONTRIBUTING

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch develop
in repository piuparts.

commit 8386e4862f909615e004b5eaaeb22a16613fc61f
Author: Holger Levsen <holger at layer-acht.org>
Date:   Tue May 20 12:24:26 2014 +0200

    Link https://piuparts.debian.org/bug_howto.html in CONTRIBUTING
---
 CONTRIBUTING | 2 +-
 TODO         | 1 -
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index f3c7d84..16998af 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -27,4 +27,4 @@ One possible workflow:
 Contributing bugs to other projects
 -----------------------------------
 Another very useful type of contributions are filing bug reports based
-on piuparts runs. This is described in FIXME and will soon be linked here.
+on piuparts runs. This is described in https://piuparts.debian.org/bug_howto.html
diff --git a/TODO b/TODO
index d3f796b..3ea062c 100644
--- a/TODO
+++ b/TODO
@@ -14,7 +14,6 @@ for 0.5x:
     copy.
   - link wiki:piuparts/UseCases||UsageTips in README_1st (after we agreed on
     a name)
-  - fix the FIXME in CONTRIBUTING
   - cleanup README_pejacevic.txt from info not related to pejacevic (eg. how
     to file bugs, how to run the slaves, etc)
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/piuparts/piuparts.git