From: Alexander Stein <alexander.stein@systec-electronic.com>
To: ptxdist@pengutronix.de
Cc: "Andreas Bießmann" <andreas.biessmann@corscience.de>,
"Matthias Klein" <matthias.klein@optimeas.de>
Subject: Re: [ptxdist] Binary patches
Date: Thu, 31 Jan 2013 11:32:56 +0100 [thread overview]
Message-ID: <3683558.9hSccScroB@ws-stein> (raw)
In-Reply-To: <51068BCA.4040806@corscience.de>
Hello Andreas,
On Monday 28 January 2013 15:31:38, Andreas Bießmann wrote:
> BTW the preferred way to fill the patches directory is:
>
> % ./p clean <package>
> % mkdir -p patches/<package>-<version>
> % touch patches/<package>-<version>/series
> % ./p extract --git <package>
> % cd platform-<config>/build-target/<package>-<version>
>
> make your changes in this git reposritory
>
> % git ptx-patches
> % cd -
> % ./p clean <package>
> % ./p extract <package>
>
> And watch the patching foo
Thanks for this instruction list. You might have added that ptx-patches is an git alias which is created automatically while patching using git. A git user not knowing about ptx-patches might get confused :)
Best regards,
Alexander
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-01-31 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 10:54 Matthias Klein
2013-01-28 13:19 ` Matthias Klein
2013-01-28 14:31 ` Andreas Bießmann
2013-01-28 14:38 ` Matthias Klein
2013-01-28 15:06 ` Andreas Bießmann
2013-01-29 8:39 ` Matthias Klein
2013-01-29 9:58 ` Andreas Bießmann
2013-01-29 10:20 ` Juergen Beisert
2013-01-29 10:26 ` Matthias Klein
2013-01-29 11:12 ` Andreas Bießmann
2013-01-29 12:06 ` Bernhard Walle
2013-01-29 12:30 ` Bernhard Walle
2013-01-29 13:29 ` Andreas Bießmann
2013-01-29 13:40 ` Bernhard Walle
2013-01-29 10:29 ` Bernhard Walle
2013-01-28 19:14 ` Robert Schwebel
2013-01-29 13:12 ` Bernhard Walle
2013-01-29 13:45 ` Matthias Klein
2013-01-31 10:32 ` Alexander Stein [this message]
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=3683558.9hSccScroB@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=andreas.biessmann@corscience.de \
--cc=matthias.klein@optimeas.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