From: "Prabhakara Rao Kolusu (WMSC-HW)" <prabhak@willowglen.asia>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Fwd: How to apply patch using ptxdist
Date: Fri, 23 Oct 2015 17:29:58 +0800 [thread overview]
Message-ID: <CAPv2-QUnBqY97LLUShMRcU5oBS4PkuTpMvbSy4GLSQUWNaiMBw@mail.gmail.com> (raw)
In-Reply-To: <201510231017.07972.jbe@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1365 bytes --]
Hi Juergen,
Thank you for prompt response.
I want to apply the patch to the existing package without extracting it
from archive file.
So that I can avoid building package from start.
For example take kernel, if I change something and want to add this to
final build, it has to be compiled from start if it needs extract to apply
the patch.
I have referred section 4.2.5, but unfortunately I did not get what I am
looking for.
Please help me in this regard.
Thanks & Regards.
Prabhakar.
On Fri, Oct 23, 2015 at 4:17 PM, Juergen Borleis <jbe@pengutronix.de> wrote:
> Hi Prabhakar,
>
> On Thursday 22 October 2015 04:48:48 Prabhakara Rao Kolusu (WMSC-HW) wrote:
> > I would like to know how to apply a patch to a already extracted package.
> > I do not want to remove the source directory of package and re extract
> it.
> >
> > Could you please help me if there is an easy method.
>
> Do you mean you want to add your patch in a persistent manner or just add
> it
> and test something?
>
> You could refer the PTXdist manual[1], section 4.2.5 for example.
>
> Regards,
> Juergen
>
> [1]
>
> http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
>
> --
> Pengutronix e.K. | Juergen Borleis
> |
> Industrial Linux Solutions | http://www.pengutronix.de/
> |
>
[-- Attachment #1.2: Type: text/html, Size: 2282 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-10-23 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPv2-QUwntMi96-M6+fQJB97RVX1-BEbDqG32paVf7QnEY6m+g@mail.gmail.com>
2015-10-22 2:48 ` Prabhakara Rao Kolusu (WMSC-HW)
2015-10-23 8:17 ` Juergen Borleis
2015-10-23 9:29 ` Prabhakara Rao Kolusu (WMSC-HW) [this message]
[not found] ` <CC2A85E271C1FB479D9C17305347F69A06C4AA54@WOLFSERVER19.wolfvision-at.intra>
2015-10-23 9:43 ` Matthias Fend
2015-10-27 2:31 ` Prabhakara Rao Kolusu (WMSC-HW)
2015-10-27 8:21 ` Juergen Borleis
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=CAPv2-QUnBqY97LLUShMRcU5oBS4PkuTpMvbSy4GLSQUWNaiMBw@mail.gmail.com \
--to=prabhak@willowglen.asia \
--cc=jbe@pengutronix.de \
--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