summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-04-06 21:57:16 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-04-06 21:57:16 +0000
commitbe34d01d50fc216e78b295b8cd362b3b9795b18f (patch)
tree9e678c0aef68de4f26b034acea3707ec2ce19feb
parent736d2e14bb46172171056de21d01f959514700c3 (diff)
web commit by JoshTriplett: Fix duplicated "moreinfo" tag.
-rw-r--r--doc/tips/issue_tracking.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tips/issue_tracking.mdwn b/doc/tips/issue_tracking.mdwn
index c6104de70..28f7ba7a1 100644
--- a/doc/tips/issue_tracking.mdwn
+++ b/doc/tips/issue_tracking.mdwn
@@ -129,8 +129,8 @@ While directories are useful for broad hierarchical
grouping, tags are better for categorizing issues
as bugs, wishlist items, security issues, patches,
or whatever other categories are useful. Bugs can
-be tagged "moreinfo", "done" "unreproducible",
-or "moreinfo", etc, to document different stages of
+be tagged "moreinfo", "done", "unreproducible",
+etc, to document different stages of
their lifecycle. A developer can take ownership of a
bug by tagging it with something like "owner/Joey".