Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
18446 articles, 1286 threads (numbers 823 – 19616) — flat view
| Advanced| Subject | Author | Date |
|---|---|---|
| Canonical URLs, truncated URLs, redirects and SEO (15 replies — unroll) | James Harris <james.harris.1@gmail.com> | 2016-01-21 16:39 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | crankypuss <invalid@invalid.invalid> | 2016-01-21 11:22 -0700 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | James Harris <james.harris.1@gmail.com> | 2016-01-22 13:58 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-21 19:16 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | James Harris <james.harris.1@gmail.com> | 2016-01-22 14:03 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Richard Yates <richard@yatesguitar.com> | 2016-01-21 12:31 -0800 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Allodoxaphobia <knock_yourself_out@example.net> | 2016-01-21 22:42 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Goran <goran@nospam.com> | 2016-01-22 13:01 +0100 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | James Harris <james.harris.1@gmail.com> | 2016-01-22 14:11 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Arno Welzel <usenet@arnowelzel.de> | 2016-01-22 17:03 +0100 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | James Harris <james.harris.1@gmail.com> | 2016-01-23 11:59 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-23 13:09 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | James Harris <james.harris.1@gmail.com> | 2016-01-23 16:17 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | "R.Wieser" <address@not.available> | 2016-01-23 20:11 +0100 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | James Harris <james.harris.1@gmail.com> | 2016-01-24 21:35 +0000 |
| → Re: Canonical URLs, truncated URLs, redirects and SEO | Eli the Bearded <*@eli.users.panix.com> | 2016-01-25 22:20 +0000 |
| .configure memory_limit building from source (20 replies — unroll) | crankypuss <invalid@invalid.invalid> | 2016-01-17 15:59 -0700 |
| → Re: .configure memory_limit building from source | "Peter H. Coffin" <hellsop@ninehells.com> | 2016-01-17 21:56 -0600 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-18 02:38 -0700 |
| → Re: .configure memory_limit building from source | "J.O. Aho" <user@example.net> | 2016-01-18 13:08 +0100 |
| → Re: .configure memory_limit building from source | Michael Vilain <vilain@NOspamcop.net> | 2016-01-18 17:48 -0800 |
| → Re: .configure memory_limit building from source | "J.O. Aho" <user@example.net> | 2016-01-19 06:56 +0100 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-19 02:37 -0700 |
| → Re: .configure memory_limit building from source | Arno Welzel <usenet@arnowelzel.de> | 2016-01-18 13:33 +0100 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-19 02:39 -0700 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-19 03:54 -0700 |
| → Re: .configure memory_limit building from source | Arno Welzel <usenet@arnowelzel.de> | 2016-01-19 18:27 +0100 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-19 14:38 -0700 |
| → Re: .configure memory_limit building from source | Arno Welzel <usenet@arnowelzel.de> | 2016-01-20 06:11 +0100 |
| → Re: .configure memory_limit building from source | Arno Welzel <usenet@arnowelzel.de> | 2016-01-19 18:22 +0100 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-19 15:25 -0700 |
| → Re: .configure memory_limit building from source | Arno Welzel <usenet@arnowelzel.de> | 2016-01-20 06:20 +0100 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-20 03:02 -0700 |
| → Re: .configure memory_limit building from source | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-21 01:43 +0100 |
| → Re: .configure memory_limit building from source | Arno Welzel <usenet@arnowelzel.de> | 2016-01-18 09:07 +0100 |
| → Re: .configure memory_limit building from source | crankypuss <invalid@invalid.invalid> | 2016-01-18 02:39 -0700 |
| → Re: .configure memory_limit building from source | Matthew Carter <m@ahungry.com> | 2016-01-18 21:21 -0500 |
| how to set default timezone as a .config argument? (22 replies — unroll) | crankypuss <invalid@invalid.invalid> | 2016-01-13 15:54 -0700 |
| → Re: how to set default timezone as a .config argument? | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 00:18 +0100 |
| → Re: how to set default timezone as a .config argument? | crankypuss <invalid@invalid.invalid> | 2016-01-14 00:13 -0700 |
| → Re: how to set default timezone as a .config argument? | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 08:45 +0100 |
| → Re: how to set default timezone as a .config argument? | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 08:49 +0100 |
| → Re: how to set default timezone as a .config argument? | crankypuss <invalid@invalid.invalid> | 2016-01-14 10:19 -0700 |
| → Re: how to set default timezone as a .config argument? | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 20:09 +0100 |
| → Re: how to set default timezone as a .config argument? | Tim Streater <timstreater@greenbee.net> | 2016-01-15 11:22 +0000 |
| → Re: how to set default timezone as a .config argument? | crankypuss <invalid@invalid.invalid> | 2016-01-15 08:53 -0700 |
| → Re: how to set default timezone as a .config argument? | Tim Streater <timstreater@greenbee.net> | 2016-01-15 17:40 +0000 |
| → PHP in a local environment (was: how to set default timezone as a .config argument?) | "Christoph M. Becker" <cmbecker69@arcor.de> | 2016-01-15 18:51 +0100 |
| → Re: PHP in a local environment (was: how to set default timezone as a .config argument?) | crankypuss <invalid@invalid.invalid> | 2016-01-15 11:00 -0700 |
| → Re: PHP in a local environment (was: how to set default timezone as a .config argument?) | Tim Streater <timstreater@greenbee.net> | 2016-01-15 20:41 +0000 |
| → Re: PHP in a local environment | "Christoph M. Becker" <cmbecker69@arcor.de> | 2016-01-17 16:36 +0100 |
| → Re: PHP in a local environment | Tim Streater <timstreater@greenbee.net> | 2016-01-17 15:54 +0000 |
| → Re: how to set default timezone as a .config argument? | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-16 01:21 +0000 |
| → Re: how to set default timezone as a .config argument? | Michael Vilain <vilain@NOspamcop.net> | 2016-01-15 18:25 -0800 |
| → Re: how to set default timezone as a .config argument? | Tim Streater <timstreater@greenbee.net> | 2016-01-16 08:25 +0000 |
| → Re: how to set default timezone as a .config argument? | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-16 11:55 +0000 |
| → Re: how to set default timezone as a .config argument? | "Christoph M. Becker" <cmbecker69@arcor.de> | 2016-01-14 11:57 +0100 |
| → Re: how to set default timezone as a .config argument? | crankypuss <invalid@invalid.invalid> | 2016-01-14 10:29 -0700 |
| → Re: how to set default timezone as a .config argument? | "Christoph M. Becker" <cmbecker69@arcor.de> | 2016-01-15 12:14 +0100 |
| → Re: how to set default timezone as a .config argument? | crankypuss <invalid@invalid.invalid> | 2016-01-15 08:57 -0700 |
| parsing print_r() output with preg_match_all() (113 replies — unroll, only first 100 listed — flat view) | "R.Wieser" <address@not.available> | 2016-01-06 17:18 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-06 19:28 +0000 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-06 20:50 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-06 21:12 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-06 16:20 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 02:23 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Matthew Carter <m@ahungry.com> | 2016-01-06 21:48 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Matthew Carter <m@ahungry.com> | 2016-01-06 21:52 -0500 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 10:20 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 10:56 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 12:55 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-07 08:36 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 13:58 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 15:33 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 15:31 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 18:23 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-06 22:50 -0500 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 10:10 +0100 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 10:03 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-07 08:38 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 14:05 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-07 13:42 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 20:24 +0000 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-07 15:27 -0500 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 09:51 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 11:18 +0000 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 14:00 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ben Bacarisse <ben.usenet@bsb.me.uk> | 2016-01-07 14:00 +0000 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 16:19 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-11 09:11 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 08:04 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-11 23:48 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-12 00:41 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 20:53 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-12 05:40 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 09:12 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-12 21:43 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 16:12 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-12 22:28 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 16:35 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-13 06:39 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-13 08:26 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 08:10 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-13 14:49 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 10:08 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-13 18:50 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 15:06 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-13 23:11 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 17:18 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-13 23:27 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 19:17 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 01:30 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 20:52 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 08:13 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-14 09:18 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 20:07 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-14 16:06 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 22:41 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-14 22:35 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ian Collins <ian-news@hotmail.com> | 2016-01-14 10:24 +1300 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 17:20 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Ian Collins <ian-news@hotmail.com> | 2016-01-14 12:14 +1300 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 19:18 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 08:34 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Anders Wegge Keller <wegge@geostat.dk> | 2016-01-14 09:20 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ian Collins <ian-news@hotmail.com> | 2016-01-14 21:56 +1300 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-14 16:08 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 22:55 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-14 16:59 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-14 23:09 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Ian Collins <ian-news@hotmail.com> | 2016-01-15 11:17 +1300 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-14 19:15 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-14 19:14 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 20:50 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-12 05:42 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-12 08:41 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 09:13 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-12 21:44 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 16:13 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-12 22:29 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 16:33 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-12 00:49 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 20:54 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 11:17 +0100 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 13:49 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 14:20 +0100 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 15:31 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 16:00 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-07 13:45 -0500 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-07 20:18 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-07 20:52 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-07 15:29 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Tim Streater <timstreater@greenbee.net> | 2016-01-07 22:42 +0000 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-08 10:43 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-11 09:07 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 08:05 -0500 |
| → Re: parsing print_r() output with preg_match_all() | Arno Welzel <usenet@arnowelzel.de> | 2016-01-11 23:51 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Thomas 'PointedEars' Lahn <PointedEars@web.de> | 2016-01-12 00:31 +0100 |
| → Re: parsing print_r() output with preg_match_all() | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 20:55 -0500 |
| → Re: parsing print_r() output with preg_match_all() | "R.Wieser" <address@not.available> | 2016-01-12 11:11 +0100 |
| Aborted connection to db: 'unconnected' user: 'fabric' host: (Got an error reading communication packets) (5 replies — unroll) | James Wang <jwang25610@gmail.com> | 2016-01-13 03:39 -0800 |
| → Re: Aborted connection to db: 'unconnected' user: 'fabric' host: (Got an error reading communication packets) | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 08:19 -0500 |
| → Re: Aborted connection to db: 'unconnected' user: 'fabric' host: (Got an error reading communication packets) | James Wang <jwang25610@gmail.com> | 2016-01-13 06:15 -0800 |
| → Re: Aborted connection to db: 'unconnected' user: 'fabric' host: (Got an error reading communication packets) | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 10:12 -0500 |
| → Re: Aborted connection to db: 'unconnected' user: 'fabric' host: (Got an error reading communication packets) | James Wang <jwang25610@gmail.com> | 2016-01-13 07:50 -0800 |
| → Re: Aborted connection to db: 'unconnected' user: 'fabric' host: (Got an error reading communication packets) | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 10:59 -0500 |
| how to configure PHP so extension_dir is null? (7 replies — unroll) | crankypuss <invalid@invalid.invalid> | 2016-01-12 07:12 -0700 |
| → Re: how to configure PHP so extension_dir is null? | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 16:25 -0500 |
| → Re: how to configure PHP so extension_dir is null? | Allodoxaphobia <knock_yourself_out@example.net> | 2016-01-13 02:09 +0000 |
| → Re: how to configure PHP so extension_dir is null? | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 21:11 -0500 |
| → Re: how to configure PHP so extension_dir is null? | crankypuss <invalid@invalid.invalid> | 2016-01-13 05:22 -0700 |
| → Re: how to configure PHP so extension_dir is null? | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 08:25 -0500 |
| → Re: how to configure PHP so extension_dir is null? | crankypuss <invalid@invalid.invalid> | 2016-01-13 07:00 -0700 |
| → Re: how to configure PHP so extension_dir is null? | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-13 10:10 -0500 |
| Build php pthreads 2 from source (11 replies — unroll) | James Wang <jwang25610@gmail.com> | 2016-01-11 03:07 -0800 |
| → Re: Build php pthreads 2 from source | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 08:14 -0500 |
| → Re: Build php pthreads 2 from source | James Wang <jwang25610@gmail.com> | 2016-01-11 06:24 -0800 |
| → Re: Build php pthreads 2 from source | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 10:01 -0500 |
| → Re: Build php pthreads 2 from source | James Wang <jwang25610@gmail.com> | 2016-01-11 07:36 -0800 |
| → Re: Build php pthreads 2 from source | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-11 12:32 -0500 |
| → Re: Build php pthreads 2 from source | James Wang <jwang25610@gmail.com> | 2016-01-12 01:58 -0800 |
| → Re: Build php pthreads 2 from source | Jerry Stuckle <jstucklex@attglobal.net> | 2016-01-12 09:04 -0500 |
| → Re: Build php pthreads 2 from source | James Wang <jwang25610@gmail.com> | 2016-01-12 06:23 -0800 |
| → Re: Build php pthreads 2 from source | "J.O. Aho" <user@example.net> | 2016-01-12 17:39 +0100 |
| → Re: Build php pthreads 2 from source | James Wang <jwang25610@gmail.com> | 2016-01-12 08:52 -0800 |
| → Re: Build php pthreads 2 from source | "J.O. Aho" <user@example.net> | 2016-01-12 21:19 +0100 |
← Newer ~Page 9 of ~50 (articles 16221–16336) Older →
csiph-web