From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: roman <roman.passler@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/openocd: bump to 0.12.0
Date: Tue, 14 Mar 2023 08:38:41 +0100 [thread overview]
Message-ID: <20230314083841.294bfd43@windsurf> (raw)
In-Reply-To: <CAJYrM9Kk8tG2x4Zpv_OPH0kQCvrv6ddgBbe7SX1S1xnKdFCH+w@mail.gmail.com>
Hello Roman,
On Tue, 14 Mar 2023 08:25:27 +0100
roman <roman.passler@gmail.com> wrote:
> The license files have been relocated to the LICENSES/* directory (available
> at https://sourceforge.net/p/openocd/code/ci/v0.12.0/tree/LICENSES/).
> The license files have been moved to the LICENSES/* directory, which can be
> found at https://sourceforge.net/p/openocd/code/ci/v0.12.0/tree/LICENSES/.
> Should they be added to the hash file, or is the COPYING file at
> https://sourceforge.net/p/openocd/code/ci/v0.12.0/tree/COPYING sufficient?
Yes, it would be good to add the files in LICENSES/ in the
OPENOCD_LICENSE variable, and therefore in the hash file as well;
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-14 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:32 [Buildroot] [PATCH 1/1] package/openocd: bump to 0.12.0 Roman Passler
2023-03-13 21:54 ` Thomas Petazzoni via buildroot
2023-03-14 7:25 ` roman
2023-03-14 7:38 ` Thomas Petazzoni via buildroot [this message]
2023-03-14 12:13 ` [Buildroot] [PATCH v2 " Roman Passler
2023-03-14 22:33 ` Thomas Petazzoni via buildroot
2023-03-15 20:44 ` Arnout Vandecappelle
2023-03-17 7:03 ` [Buildroot] [PATCH v3 " Roman Passler
2023-03-17 8:05 ` [Buildroot] [PATCH v4 " Roman Passler
2023-04-23 9:45 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2023-04-08 13:51 [Buildroot] [PATCH " Dario Binacchi
2023-04-09 13:31 ` Arnout Vandecappelle
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=20230314083841.294bfd43@windsurf \
--to=buildroot@buildroot.org \
--cc=roman.passler@gmail.com \
--cc=thomas.petazzoni@bootlin.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.