From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] poco: the Zip module depends on XML, Net and Util modules
Date: Tue, 7 Feb 2012 18:48:14 +0100 [thread overview]
Message-ID: <20120207184814.5275f6bf@skate> (raw)
In-Reply-To: <201202062310.04009.arnout@mind.be>
Le Mon, 6 Feb 2012 23:10:03 +0100,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> > This fixes the build breakage visible at:
> >
> > http://free-electrons.com/~thomas/buildroot/test-output-2011-12-02/test-920-output.bz2
> >
> > with the configuration visible at:
> >
> > http://free-electrons.com/~thomas/buildroot/test-output-2011-12-02/test-920-config
>
> Good idea to refer to the test. However, will it exist there
> forever? If not, I'm not sure if it should be in the commit message.
I can't guarantee it will be there forever, no. So indeed, next time
I'll put it after the ---.
Best regards,
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:[~2012-02-07 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 22:29 [Buildroot] [pull request] Pull request for branch for-2012.02/misc Thomas Petazzoni
2012-02-02 22:29 ` [Buildroot] [PATCH 1/2] poco: the Zip module depends on XML, Net and Util modules Thomas Petazzoni
2012-02-06 22:10 ` Arnout Vandecappelle
2012-02-07 17:48 ` Thomas Petazzoni [this message]
2012-02-02 22:29 ` [Buildroot] [PATCH 2/2] at91bootstrap: allow specification of a custom patch directory Thomas Petazzoni
2012-02-02 22:42 ` [Buildroot] [pull request] Pull request for branch for-2012.02/misc 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=20120207184814.5275f6bf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox