Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Enable vlc to run as root
Date: Wed, 16 Sep 2015 12:36:26 +0200	[thread overview]
Message-ID: <20150916123626.01f38cbd@free-electrons.com> (raw)
In-Reply-To: <712f10f4f1eb6452279b88cb749906e66f711d8a.1442391509.git.jpinto@synopsys.com>

Hello Joao,

Thanks for this new iteration. It looks good, except for one minor nit
that isn't very important, but worth mentioning.

On Wed, 16 Sep 2015 09:26:49 +0100, jpinto wrote:
> From: Joao Pinto <jpinto@synopsys.com>
> 
> A great number of embedded systems only include the root user.
> This patch has the goal of enabling vlc to be ran as root.
> 
> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
> Tested-by: Joao Pinto <jpinto@synopsys.com>

It doesn't make sense to include a Tested-by from you on your patch. We
obviously expect that you have tested your own patch. Tested-by tags
(as well as Acked-by or Reviewed-by tags) are meant to be given by
*other* developers, after testing and/or reviewing your patch.

The other minor nit is that the title of the commit still doesn't match
the Buildroot best practice, which consists in using titles having the
following format:

	<package>: <description>

So in your case, it should be:

	vlc: enable to run as root

Both issues can be fixed by the Buildroot maintainer when he applies
the patch, but I wanted to let you know so you can make things better
for your next contribution!

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-16 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  8:26 [Buildroot] [PATCH v2] Enable vlc to run as root jpinto
2015-09-16 10:36 ` Thomas Petazzoni [this message]
2015-09-16 10:38   ` Joao Pinto
2015-09-16 20:34 ` Thomas Petazzoni
2015-09-17  8:38   ` Joao Pinto

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=20150916123626.01f38cbd@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