[PEAR-CORE] cvs: pearweb /include pear-format-html.php

[Christian Weiske]

Hello Helgi,

add a wiki like patch url linking, this will most likely be only
$text =
preg_replace('/(?<=php)\s*(bug(?:fix)?|feat(?:ure)?|doc(?:umentation)?|req(?:uest)?)\s+#([0-9]+)/i',

What about just using #[0-9]+ as detection for bug numbers? trac does
it that way, and I quite like that.

And is there a way we could link changesets/commmits in cvs/svn? In
trac, just do [123] and you're linked to changeset 123 in the VCS.

[Helgi Þormar Þorbjörnsson]

Post by Christian Weiske
Hello Helgi,

add a wiki like patch url linking, this will most likely be only
$text =

preg_replace('/(?<=php)\s*(bug(?:fix)?|feat(?:ure)?|doc(?:umentation)?|req(?:uest)?)\s+#([0-9]+)/i',
What about just using #[0-9]+ as detection for bug numbers? trac does
it that way, and I quite like that.

Dunno what you read of the regex above but it should be able to do exactly
that; Well perhaps you might have to write bug #454 but well I can make that
optional if that's the case

Post by Christian Weiske
And is there a way we could link changesets/commmits in cvs/svn? In
trac, just do [123] and you're linked to changeset 123 in the VCS.

Why don't we just install Trac ? ;D Anyway it's no problem if it's just a
user writing [123] somewhere but I'd have to link only to cvs or only to svn
unless we start doing [svn:123] and such

What do you think ?

- Helgi

[Christian Weiske]

Hello Helgi,

Post by Helgi Þormar Þorbjörnsson

preg_replace('/(?<=php)\s*(bug(?:fix)?|feat(?:ure)?|doc(?:umentation)?|req(?:uest)?)\s+#([0-9]+)/i',
What about just using #[0-9]+ as detection for bug numbers? trac
does it that way, and I quite like that.

Dunno what you read of the regex above but it should be able to do
exactly that; Well perhaps you might have to write bug #454 but well
I can make that optional if that's the case

Yes, please make bug|request|doc optional.

Post by Helgi Þormar Þorbjörnsson

And is there a way we could link changesets/commmits in cvs/svn? In
trac, just do [123] and you're linked to changeset 123 in the VCS.

Why don't we just install Trac ? ;D

Because we all suffer from the not-invented-here-syndrome :)

Post by Helgi Þormar Þorbjörnsson
Anyway it's no problem if it's
just a user writing [123] somewhere but I'd have to link only to cvs
or only to svn unless we start doing [svn:123] and such

[svn:123] sounds good to me. I am not sure how cvs commits can be
linked at all, that bothers me most. Any idea?

[Helgi Þormar Þorbjörnsson]

Hibb

Post by Christian Weiske
Hello Helgi,
preg_replace('/(?<=php)\s*(bug(?:fix)?|feat(?:ure)?|doc(?:umentation)?|req(?:uest)?)\s+#([0-9]+)/i',

Post by Helgi Þormar Þorbjörnsson

Post by Christian Weiske
What about just using #[0-9]+ as detection for bug numbers? trac
does it that way, and I quite like that.

Dunno what you read of the regex above but it should be able to do
exactly that; Well perhaps you might have to write bug #454 but well
I can make that optional if that's the case

Yes, please make bug|request|doc optional.

Shall do.

Post by Christian Weiske

Post by Helgi Þormar Þorbjörnsson

Post by Christian Weiske
And is there a way we could link changesets/commmits in cvs/svn? In
trac, just do [123] and you're linked to changeset 123 in the VCS.

Why don't we just install Trac ? ;D

Because we all suffer from the not-invented-here-syndrome :)

Would mean so much less work for me haha ;D

Post by Christian Weiske

Post by Helgi Þormar Þorbjörnsson
Anyway it's no problem if it's
just a user writing [123] somewhere but I'd have to link only to cvs
or only to svn unless we start doing [svn:123] and such

[svn:123] sounds good to me. I am not sure how cvs commits can be
linked at all, that bothers me most. Any idea?

It's more tricky given each commit won't get a revision id,
[cvs:filename;revision-id] perhaps ? Feels kinda clumsy, [cvs:id] can be
achieved but ID would have to be just a news.php.net/php.pear.cvs id as in
the news entry id :-(

- Helgi