From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH] license: add overlooked license statement in bpf/GNUmakefile
Date: Thu, 5 Mar 2026 14:32:39 -0500 [thread overview]
Message-ID: <aanaV/fyspbflt37@oracle.com> (raw)
In-Reply-To: <3d9582b1-0821-7611-bd82-7a2ece8b846a@oracle.com>
On Thu, Mar 05, 2026 at 02:13:51PM -0500, Eugene Loh wrote:
> I'm confused by the end date used. Why 2024 rather than 2020 (the last
> commit?) or 2026 (today's change)?
Unfortunate copy-and-paste error. Will use 2020 since that was the only time
the file was touched.
>
> On 3/5/26 14:05, Kris Van Hees via DTrace-devel wrote:
> > Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
> > ---
> > bpf/GNUmakefile | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/bpf/GNUmakefile b/bpf/GNUmakefile
> > index 4a27e08b8..51ed7df6e 100644
> > --- a/bpf/GNUmakefile
> > +++ b/bpf/GNUmakefile
> > @@ -1,3 +1,8 @@
> > +# Oracle Linux DTrace.
> > +# Copyright (c) 2020, 2024, Oracle and/or its affiliates. All rights reserved.
> > +# Licensed under the Universal Permissive License v 1.0 as shown at
> > +# http://oss.oracle.com/licenses/upl.
> > +
> > %:
> > $(MAKE) -C .. $@
prev parent reply other threads:[~2026-03-05 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 19:05 [PATCH] license: add overlooked license statement in bpf/GNUmakefile Kris Van Hees
2026-03-05 19:13 ` [DTrace-devel] " Eugene Loh
2026-03-05 19:32 ` Kris Van Hees [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aanaV/fyspbflt37@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.