From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gupnp-tools: new package
Date: Fri, 29 Jul 2016 10:32:15 +0300 [thread overview]
Message-ID: <20160729073215.GI3588@tarshish> (raw)
In-Reply-To: <1469776607-30435-1-git-send-email-fabrice.fontaine@orange.com>
Hi Fabrice,
On Fri, Jul 29, 2016 at 09:16:47AM +0200, Fabrice Fontaine wrote:
> +ifeq ($(BR2_PACKAGE_GTKSOURCEVIEW),y)
> +GUPNP_TOOLS_DEPENDENCIES += gtksourceview
> +endif
This makes you patch depend on the patch adding the gtksourceview package. So
you should send both patches in a patch series, with the gtksourceview patch
before this one. This makes the dependency between patches clearer, making the
maintainers life easier.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2016-07-29 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 7:16 [Buildroot] [PATCH 1/1] gupnp-tools: new package Fabrice Fontaine
2016-07-29 7:32 ` Baruch Siach [this message]
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=20160729073215.GI3588@tarshish \
--to=baruch@tkos.co.il \
--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