All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] DEVELOPERS: drop package/ucl entry
Date: Wed, 28 Dec 2022 21:32:04 +0200	[thread overview]
Message-ID: <87bknn4941.fsf@tarshish> (raw)
In-Reply-To: <20221228180800.3417009-1-giulio.benetti@benettiengineering.com>

Hi Giulio,

On Wed, Dec 28 2022, Giulio Benetti wrote:
> Package ucl has been dropped with commit
> 85c5af46ad6c18841576c0f7abe241a617a44cb7
> so let's drop it from DEVELOPERS since when calling utils/get-developers
> it throws:
> WARNING: 'package/ucl/' doesn't match any file

This duplicates
http://patchwork.ozlabs.org/project/buildroot/patch/20221228083918.3762-1-fontaine.fabrice@gmail.com/

baruch

> Fixes: 85c5af46ad ("package/ucl: drop package")
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  DEVELOPERS | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 7d19bae7a6..998bac935e 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -1091,7 +1091,6 @@ F:	package/libsodium/
>  F:	package/php-amqp/
>  F:	package/python-cherrypy/
>  F:	package/sane-backends/
> -F:	package/ucl/
>  F:	package/upx/
>  F:	package/zxing-cpp/


-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-12-28 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 18:08 [Buildroot] [PATCH] DEVELOPERS: drop package/ucl entry Giulio Benetti
2022-12-28 19:32 ` Baruch Siach via buildroot [this message]
2022-12-28 20:24   ` Giulio Benetti

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=87bknn4941.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=giulio.benetti@benettiengineering.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.