On Wed, Dec 9, 2020 at 2:29 PM Vern Paxson wrote:
> It already varies with type of variable for assignments and function
> call parameters. Thus I’m puzzled at the desire for deep-copy over
> shallow-copy, given that Zeek is already primarily shallow-copy.
Same for me: wondering what's
On Mon, Oct 19, 2020 at 9:13 AM Vlad Grigorescu wrote:
> > =
> > :zeek:type:`Notice::Type`: :zeek:type:`enum`
> > =
>
> (I'm also not sure why there's a space before the last = on those lines).
It's a
On Mon, Aug 31, 2020 at 2:14 AM Robin Sommer wrote:
> - zkg:
> - Distinguish standard/recommended packages from others.
Not sure what's meant there, but names/listings would all use
`zeek/zeek-packages/` as a prefix and be a way of distinguishing.
If it's more about organizing
On Mon, Aug 24, 2020 at 6:43 AM Robin Sommer wrote:
> 1. Move each into a a separate repository on the zeek/ GitHub
>account.
>
> 2. Similar, but to avoid cluttering zeek/, create a new GitHub
>organization "zeek-packages".
I'm thinking (2). Technically, either one can