| 2012-03-25 23:22:30 |
Robert Collins |
bug |
|
|
added bug |
| 2012-03-25 23:34:20 |
Eike |
bug-repo-syncer: importance |
Undecided |
High |
|
| 2012-03-25 23:34:28 |
Eike |
bug-repo-syncer: milestone |
|
0.3.0 |
|
| 2012-03-25 23:46:14 |
Eike |
bug-repo-syncer: status |
New |
Confirmed |
|
| 2012-03-25 23:57:40 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that. |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}} |
|
| 2012-03-26 00:52:23 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}} |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[@[@BUGLINK "bug #123"@lp @]@]") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}} |
|
| 2012-03-26 01:09:18 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[@[@BUGLINK "bug #123"@lp @]@]") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}} |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[@[@BUGLINK "bug #123"@lp @]@]") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
Bug #964900
The fix should be implemented together with:
Bug #958416 (Allow Escaping of Bug-Links) |
|
| 2012-03-26 01:16:28 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[@[@BUGLINK "bug #123"@lp @]@]") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
Bug #964900
The fix should be implemented together with:
Bug #958416 (Allow Escaping of Bug-Links) |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[@[@BUGLINK "bug #123"@lp @]@]") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
The fix should be implemented together with:
bug #958416 (Allow Escaping of Bug-Links) |
|
| 2012-03-26 20:48:06 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[@[@BUGLINK "bug #123"@lp @]@]") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
The fix should be implemented together with:
bug #958416 (Allow Escaping of Bug-Links) |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
Done:
The regular expression has become more strict while implementing issue #958416
It must be preceeded and followed by a whitespce character, and there must be exactly one space character between "bug" | "issue" and "#"
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
|
| 2012-03-26 20:48:23 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "[bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
Done:
The regular expression has become more strict while implementing issue #958416
It must be preceeded and followed by a whitespce character, and there must be exactly one space character between "bug" | "issue" and "#"
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
Done:
The regular expression has become more strict while implementing issue #958416
It must be preceeded and followed by a whitespce character, and there must be exactly one space character between "bug" | "issue" and "#"
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
|
| 2012-03-26 20:57:52 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
Done:
The regular expression has become more strict while implementing issue #958416
It must be preceeded and followed by a whitespce character, and there must be exactly one space character between "bug" | "issue" and "#"
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
Done:
The regular expression has become more strict while implementing bug #958416
It must be preceeded and followed by a whitespce character, and there must be exactly one space character between "bug" | "issue" and "#"
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
|
| 2012-03-26 22:26:49 |
Eike |
bug-repo-syncer: assignee |
|
Eike (eike-welk) |
|
| 2012-03-29 04:15:14 |
Eike |
description |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
Done:
The regular expression has become more strict while implementing bug #958416
It must be preceeded and followed by a whitespce character, and there must be exactly one space character between "bug" | "issue" and "#"
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
It seems to be inserting [@[@BUGLINK "bug #123"@trac @]@] into the description. Please stop it doing that.
The regular expression for identifying bug-links (pattern "bug #123") is too
general. It matches the following text:
{{{
bug
#Un-commenting
}}}
in
{{{
lp_bug = lp_task.bug
#Un-commenting this makes the error go away.
}}}
The damaged text is in:
bug #964900
'''Done:'''
The regular expression has become more strict: The bug ID can now start with an
alphanumerical character, but all subsequent characters must be numbers, for
example: "a001". (I want one letter in the bug IDs for the test suite.)
The regular expression has become more strict while implementing bug #958416
It must be preceded by one of the characters " (", followed by one of " ).,;",
and there must be exactly one space character between "bug" and "#".
Implemented: bug #958416 (Allow Escaping of Bug-Links) |
|
| 2012-03-29 04:15:27 |
Eike |
bug-repo-syncer: status |
Confirmed |
Fix Released |
|
