From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sylpheed: Fix includedir
Date: Sun, 07 Oct 2012 13:06:22 +0200 [thread overview]
Message-ID: <5071622E.4020309@mind.be> (raw)
In-Reply-To: <50707DB6.5090401@gmail.com>
On 06/10/12 20:51, Valentine Barshak wrote:
> BTW, are there any objections to bump it to version 3.2, which is the latest. It seems to work fine for me (though to be
> honest I haven't seen any issues with 3.1 either). Version 3.2 needs the same includedir fix as well.
Not at all. Preferably as separate patches.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-10-07 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 17:25 [Buildroot] [PATCH] sylpheed: Fix includedir Valentine Barshak
2012-10-05 23:26 ` Arnout Vandecappelle
2012-10-06 18:51 ` Valentine Barshak
2012-10-07 11:06 ` Arnout Vandecappelle [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=5071622E.4020309@mind.be \
--to=arnout@mind.be \
--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