[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#501484: marked as done (www.debian.org: minor format error and command syntax clarification for control at b.d.o)

Your message dated Tue, 14 Apr 2009 16:09:10 -0700
with message-id <20090414230910.GD3310@rzlab.ucr.edu>
and subject line Re: Bug#501484: www.debian.org: minor format error and command syntax clarification for control at b.d.o
has caused the Debian Bug report #501484,
regarding www.debian.org: minor format error and command syntax clarification for control at b.d.o
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
501484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501484
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: www.debian.org
Severity: minor
Tags: patch

I made a patch for this page:
http://www.debian.org/Bugs/server-control
for reference(s) :
http://www.debian.org/Bugs/server-control#forwarded
http://www.debian.org/Bugs/server-control#notforwarded

original source from:
http://cvs.debian.org/webwml/english/Bugs/server-control.wml
[server-control.wml     1.74]

I made this patch after viewing this page and discussing the proper way to
file in bug in OFTC - #debian and #debian-www. I made a couple mistakes even
after reading the documentation. I'd like to prevent someone else from making
those mistakes. So I created the patch. I have the text of those conversations
if need be.

The diff:
1. Clarifies BTS syntax - (control at b.d.o).
2. Corrects a minor format issue in the referenced section(s).

Thanks for all you do for debian.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

278a279
>     <p>
283c284,294
<     as having been forwarded.
---
>     as having been forwarded. Where <var>address</var> may be a URL or an
>     email address. Please use a URL when possible.
>     </p>
> 
>     <p>
>     Example usage:
>     </p>
> 
>     <pre>
>           forward 123456 http://buggzz.illa.foo/cgi/007
>     </pre>
289a301
>     <p>
292a305
>     </p>

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Tue, 07 Oct 2008, Abel McClendon wrote:
> As suggested the patch file is more readable now.
> "diff -u" ;-)
> 
> see attached.

Thanks for your patch; I've resolved this with the attached change
(which slightly modifies your changes.) [Thanks to Simon Paillard for
reminding me to take a look at this bug.]


Don Armstrong

-- 
[A] theory is falsifiable [(and therefore scientific) only] if the
class of its potential falsifiers is not empty.
 -- Sir Karl Popper _The Logic of Scientific Discovery_ §21

http://www.donarmstrong.com              http://rzlab.ucr.edu

Index: english/Bugs/server-control.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/Bugs/server-control.wml,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- english/Bugs/server-control.wml	12 Feb 2009 00:58:12 -0000	1.76
+++ english/Bugs/server-control.wml	14 Apr 2009 22:49:56 -0000	1.77
@@ -276,20 +276,35 @@
   <dt><a name="forwarded"><code>forwarded</code> <var>bugnumber</var>
     <var>address</var></a></dt>
   <dd>
+    <p>
     Notes that <var>bugnumber</var> has been forwarded to the upstream
     maintainer at <var>address</var>.  This does not actually forward the
     report.  This can be used to change an existing incorrect forwarded-to
     address, or to record a new one for a bug that wasn't previously noted
-    as having been forwarded.
+    as having been forwarded. <var>address</var> should generally be a
+    URI, or possibly an email address. Using a URI where possible
+    allows tools to query a remote bug tracking system (such as
+    bugzilla) for a bug's status.
+    </p>
+
+    <p>
+      Example usage:
+    </p>
+
+    <pre>
+      forward 12345 http://bugz.illa.foo/cgi/54321
+    </pre>
   </dd>
 
 
   <dt><a name="notforwarded"><code>notforwarded</code>
     <var>bugnumber</var></a></dt>
   <dd>
+    <p>
     Forgets any idea that <var>bugnumber</var> has been forwarded to any
     upstream maintainer.  If the bug was not recorded as having been
     forwarded then this will do nothing.
+    </p>
   </dd>

--- End Message ---
Reply to: