From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] eventlog: New package
Date: Tue, 13 Oct 2015 23:56:43 +0200 [thread overview]
Message-ID: <20151013235643.556323a0@free-electrons.com> (raw)
In-Reply-To: <1443266743-20775-2-git-send-email-judge.packham@gmail.com>
Dear Chris Packham,
On Sat, 26 Sep 2015 23:25:42 +1200, Chris Packham wrote:
> eventlog is a library for creating structured events from applications,
> and is the workhorse behind syslog-ng's own messages.
>
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
> package/Config.in | 1 +
> package/eventlog/Config.in | 5 +++++
> package/eventlog/eventlog.mk | 14 ++++++++++++++
> 3 files changed, 20 insertions(+)
> create mode 100644 package/eventlog/Config.in
> create mode 100644 package/eventlog/eventlog.mk
Applied with a number of changes:
[Thomas:
- fix alphabetic ordering in package/Config.in, as noticed by
Vicente.
- rewrap Config.in help text and add some URL as a reference (though
the eventlog project doesn't seem to have a real web page)
- remove useless slash at the end of EVENTLOG_SITE
- make the license info more specific: it's a BSD-3c license
- add a hash file.]
Thanks for your contribution!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-13 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 11:25 [Buildroot] [RFC PATCH 0/2] Syslog-ng Chris Packham
2015-09-26 11:25 ` [Buildroot] [RFC PATCH 1/2] eventlog: New package Chris Packham
2015-09-28 10:43 ` Vicente Olivert Riera
2015-10-13 21:56 ` Thomas Petazzoni [this message]
2015-09-26 11:25 ` [Buildroot] [RFC PATCH 2/2] syslog-ng: " Chris Packham
2015-09-26 11:35 ` Chris Packham
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=20151013235643.556323a0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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