mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Patch creation
Date: Tue, 26 Jun 2018 08:23:03 +0200	[thread overview]
Message-ID: <5207290.jiuQB2Rjvd@ada> (raw)
In-Reply-To: <20180625200447.7rnz563uie3bp7nj@pengutronix.de>

Hei hei,

Am Montag, 25. Juni 2018, 22:04:47 CEST schrieb Uwe Kleine-König:
> On Mon, Jun 25, 2018 at 09:28:10AM -0500, Crim, Jason wrote:
> > Is there good documentation that someone can point me to for generating
> > a patch and updating the series file?
> 
> If there is already a patch stack, just do:

If there is none, in your BSP create a subfolder patches, and in that a 
subfolder '$yourpackage-1.2.3', use the same folder name as your package has 
in your folder 'platform-$yourplatform/build-target'. Put the patches and a 
series file inside. All that before you call `ptxdist --git extract 
$yourpackage`.

> 	ptxdist clean $yourpackage
> 	ptxdist extract --git $yourpackage
> 	cd platform-*/build-target/$yourpackage-1.2.3
> 	vi somefile
> 	git add somefile
> 	git commit
> 	git ptx-patches

All that is described in the documentation section 4.2 "Creating Patches for a 
Package": https://www.ptxdist.org/doc/dev_manual.html#using-git

If you need special patch numbering and tags in the series file, have a look 
at the patches distributed with ptxdist and search the mailinglist archive. 
IIRC Michael explained how to do that in the past.

Greets
Alex


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-06-26  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 14:28 Crim, Jason
2018-06-25 20:04 ` Uwe Kleine-König
2018-06-26  6:23   ` Alexander Dahl [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=5207290.jiuQB2Rjvd@ada \
    --to=ada@thorsis.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