From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iftop: new package
Date: Mon, 21 Jan 2013 18:48:53 +0100 [thread overview]
Message-ID: <20130121184853.0174d33d@skate> (raw)
In-Reply-To: <1358796288-17403-1-git-send-email-bogdan@nimblex.net>
Dear Bogdan Radulescu,
On Mon, 21 Jan 2013 19:24:48 +0000, Bogdan Radulescu wrote:
> I adjusted my patch and yes, the correct way is very nice :)
> I was at the mountains and I didn't have my computer to send the
> adjustment earlier. Thanks for you advice!
You shouldn't put such a message here in the commit log: it will be
preserved forever in the Git history. If you want to send such
informations, either use an introduction e-mail (separate from the
e-mail carrying the patch itself), or for a single patch, put your
"personal" comments...
>
>
> Signed-off-by: Bogdan Radulescu <bogdan@nimblex.net>
> ---
... here. I.e, after the --- line.
> +config BR2_PACKAGE_IFTOP
> + bool "iftop"
> + select BR2_PACKAGE_NCURSES
> + select BR2_PACKAGE_LIBPCAP
> + select BR2_INET_IPV6
No. Please look at how other packages do it for BR2_INET_IPV6. You're
not allowed to select it. You should depend on it, and show a comment
when BR2_INET_IPV6 is not available.
> +
> + help
No empty line between the bool/select/depends on line and the help line.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-21 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:49 [Buildroot] [PATCH] iftop: new package Bogdan Radulescu
2013-01-16 15:49 ` Bogdan Radulescu
2013-01-16 13:55 ` Thomas Petazzoni
2013-01-16 14:11 ` Peter Korsgaard
2013-01-20 20:50 ` Peter Korsgaard
2013-01-21 19:24 ` Bogdan Radulescu
2013-01-21 17:48 ` Thomas Petazzoni [this message]
2013-01-21 20:40 ` Bogdan Radulescu
2013-01-21 21:59 ` Peter Korsgaard
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=20130121184853.0174d33d@skate \
--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 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.