All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] gnupg: depend on libiconv if appropriate
Date: Tue, 04 Feb 2014 11:25:39 +0100	[thread overview]
Message-ID: <878utrdvj0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <52F0BCEC.6000905@mind.be> (Arnout Vandecappelle's message of "Tue, 04 Feb 2014 11:11:56 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 04/02/14 10:59, Arnout Vandecappelle wrote:
 >> On 30/12/13 18:57, Bernd Kuhls wrote:
 >>> 
 >>> Signed-off-by: Bernd Kuhls <berndkuhls@hotmail.com>
 >> 
 >> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
 >> 
 >> Ideally, the explanation that you put in the follow-up message should be
 >> in the commit log, but OK.

 >  Actually, Bernd, to make our life easier, could you repost your
 > iconv-related patches (including the one in xorg) with the following inj
 > the commit message:

 > If iconv is built before this package, this package will link against it;
 > if it is built after this package, it will not be linked against it. To
 > make the build reproducible, make sure that iconv is always built before
 > this package.

True. I already applied the gnupg patch (but didn't push it), so I've
adjusted the commit message to match.

Bernd, could you resend the other patches with that commit message -
Thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-04 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 17:57 [Buildroot] [PATCH 1/3] gnupg: depend on libiconv if appropriate Bernd Kuhls
2014-02-02 16:51 ` Bernd Kuhls
2014-02-04  9:59 ` Arnout Vandecappelle
2014-02-04 10:11   ` Arnout Vandecappelle
2014-02-04 10:25     ` Peter Korsgaard [this message]
2014-02-04 10:24   ` 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=878utrdvj0.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.