From: maximilian attems <max@stro.at>
To: Michal Marek <mmarek@suse.cz>
Cc: Livio Soares <livio@eecg.toronto.edu>,
Theodore Ts'o <tytso@mit.edu>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Fix for scripts/builddeb (non-x86, and with output option)
Date: Tue, 18 Jan 2011 12:24:13 +0100 [thread overview]
Message-ID: <20110118112413.GA12794@stro.at> (raw)
In-Reply-To: <4D34C38F.70807@suse.cz>
On Mon, 17 Jan 2011, Michal Marek wrote:
> > Date: Mon, 17 Jan 2011 15:29:06 -0500
> > Subject: [PATCH] Two fixes to builddeb script, regarding the built of header package:
> >
> > 1) Previous behavior assumed the build was executed inside the
> > source tree (no 'O=' option).
this seems worthwile, but didn't check the implementation detail.
> > 2) Previous behavior assumed 'x86' architecture.
this is fixed in linux-kbuild.git
could you please repost on top of latest, thank you.
--
maks
next prev parent reply other threads:[~2011-01-18 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D34C237.306@eecg.toronto.edu>
2011-01-17 22:32 ` [PATCH] Fix for scripts/builddeb (non-x86, and with output option) Michal Marek
2011-01-18 11:24 ` maximilian attems [this message]
2011-01-18 14:00 ` maximilian attems
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=20110118112413.GA12794@stro.at \
--to=max@stro.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=livio@eecg.toronto.edu \
--cc=mmarek@suse.cz \
--cc=tytso@mit.edu \
/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