X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=beyond-pkging.dbk;h=25987fed41c857998ac0f92207fa3a9b1aff4ffc;hp=371fba21d3b1e20e312448a2b0245795af0cb062;hb=8f2b1802ba79cc398b93894ac9b1568d4beafe40;hpb=8e5bea309b68373c2d1e2038f22cd2ce241018c0 diff --git a/beyond-pkging.dbk b/beyond-pkging.dbk index 371fba2..25987fe 100644 --- a/beyond-pkging.dbk +++ b/beyond-pkging.dbk @@ -40,7 +40,7 @@ generally ease the process. Make sure the bug is not already filed against a package. Each package has a bug list easily reachable at -http://&bugs-host;/packagename. +https://&bugs-host;/packagename. Utilities like querybts 1 can also provide you with this information (and reportbug will usually invoke @@ -64,7 +64,7 @@ From time to time you may want to check what has been going on with the bug reports that you submitted. Take this opportunity to close those that you can't reproduce anymore. To find out all the bugs you submitted, you just have to visit -http://&bugs-host;/from:your-email-addr. +https://&bugs-host;/from:your-email-addr.
Reporting lots of bugs at once (mass bug filing) @@ -126,7 +126,7 @@ your intention there. To view bugs tagged with a specific usertag, visit -http://&bugs-host;/cgi-bin/pkgreport.cgi?users=email-addr&tag=tag-name. +https://&bugs-host;/cgi-bin/pkgreport.cgi?users=email-addr&tag=tag-name.
@@ -407,7 +407,7 @@ list of points to check in your review. You can find more checks in the wiki where several developers share their own -sponsorship checklists. +sponsorship checklists.