From: maximilian attems <max@stro.at>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org,
"Nikolai Kondrashov" <spbnick@gmail.com>,
"Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
Subject: Re: [PATCH] deb-pkg: Fix building outside of source tree (O=...).
Date: Wed, 2 Feb 2011 09:51:27 +0000 [thread overview]
Message-ID: <20110202095127.GG19835@vostochny.stro.at> (raw)
In-Reply-To: <4D492525.20402@gmail.com>
Hello Michal,
On Wed, Feb 02, 2011 at 10:34:29AM +0100, Nicolas de Pesloüan wrote:
> Le 24/01/2011 14:41, Nicolas de Pesloüan a écrit :
>
> Hi Michal,
>
> Any troubles with my patch? I still don't find it in any branchs of
> git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git
>
> It depends on commit 1b9a50d931a04ba007cc1a926fead3ff4b5afa9b, from
> Maximilian Attems, (in for-next), because it changes the same lines in
> scripts/package/builddeb.
>
> But, as the problem it fixes cause make deb-pkg to fail, it might be pushed to rc-fixes... ?
>
> Do you want me to rebase it on rc-fixes? (This would cause a future merge
> to fail when applying the patch from Maximilian, but...).
Indeed it be cool to have those fixes landed for 2.6.38.
I was already a bit upset by your policy to root any deb-pkg
for the next release cycle (the umask fix for example).
Especially considering that the first one of aboves listed fixes
is a *oneliner*.
Without these 2 fixes it is hard to recommmend to our users to use deb-pkg.
They are needed for a working make deb-pkg in 2.6.38.
thank you
--
maks
next prev parent reply other threads:[~2011-02-02 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:41 [PATCH] deb-pkg: Fix building outside of source tree (O=...) Nicolas de Pesloüan
2011-01-26 9:52 ` maximilian attems
2011-02-02 9:34 ` Nicolas de Pesloüan
2011-02-02 9:51 ` maximilian attems [this message]
2011-02-04 14:12 ` Michal Marek
2011-01-26 8:46 Nikolai Kondrashov
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=20110202095127.GG19835@vostochny.stro.at \
--to=max@stro.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nicolas.2p.debian@gmail.com \
--cc=spbnick@gmail.com \
/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.