From: "Krishnanjanappa, Jagadeesh" <Jagadeesh.Krishnanjanappa@caviumnetworks.com>
To: Anders Darander <anders@chargestorm.se>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dpkg: add triplet entry to fix build error for armeb
Date: Wed, 8 Apr 2015 14:43:52 +0000 [thread overview]
Message-ID: <1428504230941.43152@caviumnetworks.com> (raw)
In-Reply-To: <20150408134320.GB8848@ad.chargestorm.se>
>Drop INC_PR from this patch.
>There's no INC_PR in the .inc file, and besides that, we're not touching
>PR at all, unless we're really forced to.
Yes, there is no INC_PR defined in dpkg.inc file.
The intention was if anyone wants to update dpkg.inc file in future, they
can define INC_PR in dpkg.inc file and then the updated INC_PR value
will be reflected in recipe file. I felt this would help to track changes in
dpkg application build.
However, I have sent Patch v2 with INC_PR, PR removed.
Thanks,
Jagadeesh
_____________________________________
From: Anders Darander <anders@chargestorm.se>
Sent: Wednesday, April 8, 2015 7:13 PM
To: Krishnanjanappa, Jagadeesh
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] dpkg: add triplet entry to fix build error for armeb
* Krishnanjanappa, Jagadeesh <jagadeesh.krishnanjanappa@caviumnetworks.com> [150408 15:33]:
> 2. Added INC_PR to PR to have an updated value, when INC_PR is defined
> in dpkg.inc file
Drop INC_PR from this patch.
There's no INC_PR in the .inc file, and besides that, we're not touching
PR at all, unless we're really forced to.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
next prev parent reply other threads:[~2015-04-08 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 13:33 [PATCH] dpkg: add triplet entry to fix build error for armeb Krishnanjanappa, Jagadeesh
2015-04-08 13:43 ` Anders Darander
2015-04-08 14:43 ` Krishnanjanappa, Jagadeesh [this message]
2015-04-08 15:06 ` Otavio Salvador
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=1428504230941.43152@caviumnetworks.com \
--to=jagadeesh.krishnanjanappa@caviumnetworks.com \
--cc=anders@chargestorm.se \
--cc=openembedded-core@lists.openembedded.org \
/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