Quick question: what kind of type / data are we considering here? If you
can specify
things like "acl bar int 1234" & "acl bar ipaddr 1.2.3.4", I want this &
I want it now!
But I'm guessing this is not what you mean.
Second thing: I get this from CVS
cvs server: Up-to-date check failed for `src/acl.c'
cvs server: Up-to-date check failed for `src/protos.h'
cvs server: Up-to-date check failed for `src/structs.h'
cvs [server aborted]: correct above errors first!
cvs commit: saving log message in /tmp/cvsJdlZXt
when trying to commit my branch (that I first committed mistakenly
to source forge head, then mkcvsbranch rvenning_tosacl, then
cvs commit again). Any ideas how to fix?
Roger.
Robert Collins wrote:
> ----- Original Message -----
> From: "Henrik Nordstrom" <hno@hem.passagen.se>
> To: "Robert Collins" <robert.collins@itdomain.com.au>
> Cc: <squid-dev@squid-cache.org>
> Sent: Sunday, April 01, 2001 10:42 AM
> Subject: Re: plugin parsing code and acl lists
>
>
>> Robert Collins wrote:
>>
>>> I have a choice to make: I can change
>>> acl foo type data
>>> acl foo type data
>>> ...
>>> to
>>> acl foo type
>>> acl foo data
>>
>> ...
>>
>>> Are there any preferences ?
>>
>> My preference is to have the type always listed, and barf loudly if
>
> the
>
>> user is stupid and does not know what he/she is doing. I think it is
>> less error prone that way, and surely less confusing when seeing
>
> config
>
>> fragments..
>
>
> Ok. Any other input?
>
>> Also it allows for things like this without worry:
>>
>> #acl foo type data
>> acl foo type moredata
>> acl foo type ...
>> #acl foo type otherdata
>> acl foo type evenmoredata
>
>
> Which would be
> acl foo type
> acl foo data
> acl foo evenmoredata
> ac foo evenmoremoredata
>
> Rob
>
>> /Henrik
>>
>>
-- ------------------------------------------------------------- Roger Venning \ Do not go gentle into that good night Melbourne \ Rage, rage against the dying of the light. Australia <r.venning@bipond.com> Dylan ThomasReceived on Sun Apr 01 2001 - 03:06:25 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:43 MST