From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/tinyproxy: new package
Date: Sun, 15 Mar 2020 23:07:39 +0100 [thread overview]
Message-ID: <20200315230739.67c238b5@windsurf.home> (raw)
In-Reply-To: <20200314102323.1781-1-alexander.i.mukhin@gmail.com>
On Sat, 14 Mar 2020 13:23:23 +0300
Alexander Mukhin <alexander.i.mukhin@gmail.com> wrote:
> Tinyproxy is a small, efficient HTTP/SSL proxy daemon.
>
> https://tinyproxy.github.io
>
> Signed-off-by: Alexander Mukhin <alexander.i.mukhin@gmail.com>
> ---
> DEVELOPERS | 3 +++
> package/Config.in | 1 +
> .../0001-Makefile.am-remove-docs-subdir.patch | 27 +++++++++++++++++++
> package/tinyproxy/Config.in | 16 +++++++++++
> package/tinyproxy/tinyproxy.hash | 2 ++
> package/tinyproxy/tinyproxy.mk | 15 +++++++++++
> 6 files changed, 64 insertions(+)
> create mode 100644 package/tinyproxy/0001-Makefile.am-remove-docs-subdir.patch
> create mode 100644 package/tinyproxy/Config.in
> create mode 100644 package/tinyproxy/tinyproxy.hash
> create mode 100644 package/tinyproxy/tinyproxy.mk
Applied to master, thanks. Thanks Peter Seiderer for the review.
Alexander: could you submit a patch upstream that adds --disable-doc
option, or that detects the availability of asciidoc before building
the documentation ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-03-15 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 21:05 [Buildroot] [PATCH] tinyproxy: New package Peter Seiderer
2020-03-14 10:23 ` [Buildroot] [PATCH] package/tinyproxy: new package Alexander Mukhin
2020-03-15 17:41 ` Peter Seiderer
2020-03-15 22:07 ` Thomas Petazzoni [this message]
2020-03-19 14:04 ` [Buildroot] [PATCH] package/tinyproxy: use the release tarball, not a git clone Alexander Mukhin
2020-03-19 17:58 ` Yann E. MORIN
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=20200315230739.67c238b5@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox