 | | Re: A Community Problem (Was: Re: 10152 Update)
|
|
(...) I'm not sure it qualifies as an actual "press release", but what I think we've been referring to is Jake's post on Lugnet: (URL) the post on 1000steine, which supposedly had very similar content: (URL) almost vaugely remember this set being on (...) (19 years ago, 29-Dec-04, to lugnet.lego)
|
| |
| | Re: A Community Problem (Was: Re: 10152 Update)
|
|
"David Eaton" <deaton@intdata.com> wrote in message news:I9GuDD.nKo@lugnet.com... [ ... snipped ... ] (...) we've (...) [ ... snipped ... ] Neither of these posts by LEGO employees is a Press Release. If these posts are what Ken is referring to as (...) (19 years ago, 29-Dec-04, to lugnet.lego)
|
| |
| | Re: A Community Problem (Was: Re: 10152 Update)
|
|
(...) Obviously at this point the press release has been pulled. I was virtuly identical as the post Jake put up acting as a representitive of TLC. It was also marketed so by SHO and the "limited" aspect was played up there more than anywhere. (...) (19 years ago, 29-Dec-04, to lugnet.lego)
|
| |
| | Re: A Community Problem (Was: Re: 10152 Update)
|
|
(...) This is laughable. It would be near impossible for a company to make a press release disappear. When comapnies issue press releases they go out over the wire and news sources pick them up. So if LEGO did remove a copy of a press release form (...) (19 years ago, 29-Dec-04, to lugnet.lego)
|
| |
| | Re: A Community Problem (Was: Re: 10152 Update)
|
|
(...) SNIP (...) Laughable that their web sit periodicaly changes? You'll note that the link you provided does not cover every press realease ever released. That does not mean that it did not exist. -Ken (19 years ago, 30-Dec-04, to lugnet.lego)
|
