[p4] Mailing list question - posts seem to take longer than expected to show through list

[Looney, James B]

Why is it that posts seem to take a very, very, very long time to show
back up through the mailing list?

- Below, Jay's email shows that he sent it on 11/06/2007 at 11:05am.
- I received that email through the Perforce mailing list at 3:15pm.
- I responded at 3:28pm (the email below shows 2:28pm, so I'm guessing
there's a time zone change somewhere).
- My email didn't show up on the list until 11/07/2007 at 12:46am.

Even looking at the times +/- one hour (for time zone changes), it still
takes a very long time for those emails to make it through.  Anyone know
why it takes so long?  When I post through any Python mailing list, it
shows up in about 5 minutes.

(Just because I'm curious...) I'm sending this 11/07/2007 at 8:04am,
Mountain time.

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Looney, James B
> Sent: Tuesday, November 06, 2007 2:28 PM
> To: Jay Glanville; Perforce Users Mailing List
> Subject: Re: [p4] (no subject)
> 
> Why not use a trigger to check the LineEnd value when the user
> creates/edits
> the workspace?  That'd cover future workspace 
> creation/updates, although
> it's fairly easy to write a script that can also go through 
> all clients
> checking the LineEnd value and either reporting or changing it. 
> 
> -James
> 
> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com 
> > [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Jay Glanville
> > Sent: Tuesday, November 06, 2007 11:05 AM
> > To: Perforce Users Mailing List
> > Subject: [p4] (no subject)
> > 
> > Hello all,
> > 
> > What, in your opinion, is the best way to prevent users from 
> > submitting
> > text files that use the 'wrong' (ie: Window's CR/LF) line 
> > ending style?
> > 
> > I've told all my P4 users that they should be using the 'share' line
> > ending property for their workspaces, but there's always one 
> > in a bunch
> > who'll forget.
> > 
> > My first thought was to write a trigger that would check all 
> > text files
> > on check in, but that might get a little onerous on the server,
> > especially when creating a new branch with 17,000 files in it.
> > 
> > Any suggestions I haven't thought of?
> > 
> > Thanks
> > 
> > JDG
> > 
> > ---
> > Jay Dickon Glanville
> > 
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> > 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>