5509HYTi3-038kEHp0343ZAIO1-963kwgB1395UPuh9-001aCDl0273YfdP5-732pgQR0842KQtd7-217Qhl78
[Fwd: Married, Lonely, and home alone!
Looking for a no-strings relationship ?
How about a lonely, HOT, married woman?
This site was started by a married woman, run by
married women.
They are for real, they a
What about people getting the list as a digest? Also, the spam ends
up in the mail archives.
On Sat, 15 Feb 2003, D. Hageman wrote:
>
> I have only been glancing at this thread, but basically it comes down to
> this - If the spam bothers you that much setup spam filtering on your
> personal
On Sat, Feb 15, 2003 at 01:24:26PM -0600, D. Hageman wrote:
>... We played around with using Screens and driver
> names, but in the end we were looking at keying off the device identifier.
> At this time I still believe that is the best thing to use, but we have
> no way at this time of grabbin
I have only been glancing at this thread, but basically it comes down to
this - If the spam bothers you that much setup spam filtering on your
personal machine and be done with it. We waste more time and bandwidth
talking about what "should" be done (with the list) then actually doing
what re
Speaking of Dri-patches... ;)
There seems to be a problem with the @users.sourceforge.net wildcard
address in the subscriber list. I'm subscribed to Dri-patches, but not
with my sourceforge email.
--
Leif Delgass
http://www.retinalburn.net
-- Forwarded message --
Date: Sat, 15
On Sat, 15 Feb 2003, Mike A. Harris wrote:
> On Fri, 14 Feb 2003, Leif Delgass wrote:
>
> >> I could do it, but I don't think it's a good idea to restrict those
> >> who are non-members of the list. Cross postings from the xfree86 lists
> >> are sometimes useful.
> >>
> >> Alan.
> >
> >What abou
On 15 Feb 2003, Eric Anholt wrote:
> On Tue, 2003-02-11 at 20:11, Leif Delgass wrote:
> > I've opened a new mach64 branch (mach64-0-0-6-branch), which has now been
> > updated from the current DRI trunk with X 4.2.99.2 and Mesa 5.x. I've
> > updated the mach64 driver to Mesa 5 based on the chang
On Sat, 15 Feb 2003, David D. Hagood wrote:
>Date: Sat, 15 Feb 2003 09:23:08 -0600
>From: David D. Hagood <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Content-Type: text/plain; charset=us-ascii; format=flowed
>List-Id:
>Subject: Re: DRI Mailing list maintanence / maintaner
>
>Could the list be set
On Fri, 14 Feb 2003, Leif Delgass wrote:
>> I could do it, but I don't think it's a good idea to restrict those
>> who are non-members of the list. Cross postings from the xfree86 lists
>> are sometimes useful.
>>
>> Alan.
>
>What about dri-patches? It gets all the same spam that -devel and -use
Hello,
I'm experiencing the following behavior on my IBM A20p ThinkPad with an ATI
Rage Mobility M3 video card, running XFree86-4.2. When certain GL
screensavers are running, the entire system locks up (requiring a hard boot)
when the messaging client I'm using (KMess 0.9.8, for KDE 3.x) draws
On Tue, 2003-02-11 at 20:11, Leif Delgass wrote:
> I've opened a new mach64 branch (mach64-0-0-6-branch), which has now been
> updated from the current DRI trunk with X 4.2.99.2 and Mesa 5.x. I've
> updated the mach64 driver to Mesa 5 based on the changes to the Rage 128
> driver. Testing hasn't
On Fri, Feb 14, 2003 at 08:35:02PM -0500, Leif Delgass wrote:
> On Sat, 15 Feb 2003, Alan Hourihane wrote:
>
> > On Fri, Feb 14, 2003 at 03:34:45 -0700, Brian Paul wrote:
> > > Smitty wrote:
> > > >Hi Rich
> > > >
> > > >
> > > >>>Is there anything that can be done to cut down the spam on dri-deve
On Fri, Feb 14, 2003 at 06:24:50PM -0500, Leif Delgass wrote:
>On Fri, 14 Feb 2003, David Dawes wrote:
>
>[snip]
>
>> There are some more serious things holding up 4.3, including the issue
>> that Leif mentioned here a couple of days ago. I haven't seen anyone
>> comment on his proposed solution f
Felix and I have been slowing working on a more solidified design of
the DRI configuration idea that has been discussed on this list a couple
of times. During our last public discussion in which we were talking
about configuration file formats we attempted to find a item in which to
key every
Could the list be set up to:
1) maintain a list of email addresses that have been verified GOOD.
2) maintain a list of email addresses that have been verified BAD (e.g.
[EMAIL PROTECTED]).
3) Check all inbound messages, such that:
3a) If the message is from an email subscribed to the list, ACCEP
15 matches
Mail list logo
