Re: Interwiki features supported in the squid wiki

Kinkie wrote: Hi all wiki editors, I've stumbled across a functionality of the wiki engine I hadn't really explored before: interwiki links. That's special keywords which get translated to external links. Some of the most useful I found are: Bug:# (e.g. Bug:123) points to the Squid

Re: Build failed in Hudson: 2.HEAD-i386-Debian-sid #57

n...@squid-cache.org wrote: See http://build.squid-cache.org/job/2.HEAD-i386-Debian-sid/57/ -- Started by upstream project 2.HEAD-amd64-CentOS-5.3 build number 118 Building remotely on rio.treenet cvs [checkout aborted]: Name or service not known FATAL:

wiki, bugzilla, feature requests

AIUI we use the wiki [over and above being a source of docs] to /design features/ and manage [the little] scheduling that we, as volunteers can do. I think thats great. However, we also have many bugs that are not strictly-current-defects. They are wishlist items. What should we do here? I've

Re: Interwiki features supported in the squid wiki

On Tue, Sep 22, 2009 at 2:06 PM, Amos Jeffries squ...@treenet.co.nz wrote: Kinkie wrote: Hi all wiki editors,  I've stumbled across a functionality of the wiki engine I hadn't really explored before: interwiki links. That's special keywords which get translated to external links. Some of

[PATCH] parameterize deny_info URL redirect

It's long been an annoyance that deny_info will only accept the full canonical URL requested via the %s parameter. Yet the error pages have a full range of request and other details available to them. That problem severely limits the possibilities of replacing url_rewrite redirect with an

Hudson build is back to normal: 2.HEAD-i386-Debian-sid #59

See http://build.squid-cache.org/job/2.HEAD-i386-Debian-sid/59/

Build failed in Hudson: 3.HEAD-i386-Debian-sid #56

See http://build.squid-cache.org/job/3.HEAD-i386-Debian-sid/56/ -- Started by upstream project 3.HEAD-amd64-CentOS-5.3 build number 111 Building remotely on rio.treenet bzr: ERROR: Connection error: while sending POST

Re: wiki, bugzilla, feature requests

Robert Collins wrote: AIUI we use the wiki [over and above being a source of docs] to /design features/ and manage [the little] scheduling that we, as volunteers can do. I think thats great. However, we also have many bugs that are not strictly-current-defects. They are wishlist items. What

Re: wiki, bugzilla, feature requests

I'm proposing: - if there is a bug for something, and a wiki page, link them together. - scheduling, assignment, and dependency data should be put in bugs - whiteboards to sketch annotate document etc should always be in the wiki -Rob signature.asc Description: This is a digitally signed

Re: Build failed in Hudson: 2.HEAD-i386-Debian-sid #57

ons 2009-09-23 klockan 00:07 +1200 skrev Amos Jeffries: n...@squid-cache.org wrote: See http://build.squid-cache.org/job/2.HEAD-i386-Debian-sid/57/ -- Started by upstream project 2.HEAD-amd64-CentOS-5.3 build number 118 Building remotely on

Re: wiki, bugzilla, feature requests

tis 2009-09-22 klockan 23:27 +1000 skrev Robert Collins: I'm proposing: - if there is a bug for something, and a wiki page, link them together. - scheduling, assignment, and dependency data should be put in bugs - whiteboards to sketch annotate document etc should always be in the wiki I

Build failed in Hudson: 2.HEAD-i386-Debian-sid #63

See http://build.squid-cache.org/job/2.HEAD-i386-Debian-sid/63/ -- Started by user amos Building remotely on rio.treenet cvs checkout: CVS password file /home/www/squid/.cvspass does not exist - creating a new file cvs checkout: authorization failed:

Build failed in Hudson: 3.HEAD-i386-Debian-sid #57

See http://build.squid-cache.org/job/3.HEAD-i386-Debian-sid/57/ -- Started by user amos Building remotely on rio.treenet bzr: ERROR: Invalid http response for http://www.squid-cache.org/bzr/squid3/trunk/.bzr/branch-format: Bad status line received Using