From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/perl-image-exiftool: new package
Date: Thu, 29 Dec 2022 10:29:54 +0100 [thread overview]
Message-ID: <20221229102954.2785314e@windsurf> (raw)
In-Reply-To: <20221219213343.26475-1-ps.report@gmx.net>
Hello Peter,
On Mon, 19 Dec 2022 22:33:43 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/Config.in | 1 +
> package/perl-image-exiftool/Config.in | 8 ++++++++
> .../perl-image-exiftool/perl-image-exiftool.hash | 6 ++++++
> package/perl-image-exiftool/perl-image-exiftool.mk | 14 ++++++++++++++
> 4 files changed, 29 insertions(+)
> create mode 100644 package/perl-image-exiftool/Config.in
> create mode 100644 package/perl-image-exiftool/perl-image-exiftool.hash
> create mode 100644 package/perl-image-exiftool/perl-image-exiftool.mk
I've applied to master, but then later realized that you had not added
an entry in the DEVELOPERS file for this package. And you actually
dropped your entire DEVELOPERS entry a few months ago.
So what do we do? You submit new packages, but you're not ready to
maintain them? :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-29 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 21:33 [Buildroot] [PATCH v1] package/perl-image-exiftool: new package Peter Seiderer
2022-12-29 9:29 ` Thomas Petazzoni via buildroot [this message]
2023-01-05 13:41 ` Peter Seiderer
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=20221229102954.2785314e@windsurf \
--to=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
--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.