From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist-2012.03.0 some python development files could not be found
Date: Tue, 22 Apr 2014 14:24:10 +0200 [thread overview]
Message-ID: <20140422122408.GA16277@omega> (raw)
In-Reply-To: <9680960ed12803245dfdcd4197375e74@dcl.com.tr>
Got it now...
next time I need to take a closer look on other patches... was very
stupid and I didn't realize that the behaviour to check on python-dev
was different in older ptxdist releases...
Nevertheless it's much easier to detect the issue when I have the exact
sambe behaviour which I have now...
Try a:
git cherry-pick c498184 2a89985
instead of:
git cherry-pick 2a89985
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-22 12:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 8:48 bilal.tas
2014-04-22 9:09 ` Alexander Aring
2014-04-22 9:19 ` [ptxdist] ptxdist-2012.03.0 some python development filescouldnot " bilal.tas
2014-04-22 9:25 ` Alexander Aring
2014-04-22 9:28 ` Alexander Aring
2014-04-22 9:35 ` [ptxdist] ptxdist-2012.03.0 some pythondevelopmentfilescouldnot " bilal.tas
2014-04-22 9:41 ` Alexander Aring
2014-04-22 9:50 ` [ptxdist] ptxdist-2012.03.0 somepythondevelopmentfilescouldnotbe found bilal.tas
2014-04-22 9:57 ` Alexander Aring
2014-04-22 10:02 ` [ptxdist] ptxdist-2012.03.0somepythondevelopmentfilescouldnotbefound bilal.tas
2014-04-22 11:18 ` Alexander Aring
2014-04-22 11:25 ` bilal.tas
2014-04-22 11:27 ` Alexander Aring
2014-04-22 11:33 ` bilal.tas
2014-04-22 11:50 ` Alexander Aring
2014-04-22 9:35 ` [ptxdist] ptxdist-2012.03.0 some python development filescouldnot be found Marc Kleine-Budde
2014-04-22 9:37 ` Alexander Aring
2014-04-22 9:37 ` [ptxdist] ptxdist-2012.03.0 some pythondevelopmentfilescouldnot " bilal.tas
2014-04-22 12:24 ` Alexander Aring [this message]
2014-04-23 6:34 ` [ptxdist] ptxdist-2012.03.0 some python development files couldnot " Bilal TAŞ
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=20140422122408.GA16277@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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