From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] add some patches with fixes, partly queued upstream
Date: Mon, 24 Mar 2014 09:41:53 +0100 [thread overview]
Message-ID: <20140324084153.GA10959@pengutronix.de> (raw)
In-Reply-To: <088f5892e63bdae1b81e6ed7f2dd7d69@idefix.lespocky.dyndns.org>
Hi,
On Fri, Mar 21, 2014 at 02:35:16PM +0100, Alexander Dahl wrote:
> Am 2014-03-19 10:49, schrieb Michael Olbrich:
> > Can you replace our patches with whatever was applied upstream? That will
> > make it easier in the future if we ever get a release.
> > And mark them as upstream (like patches/opkg-utils-r4747/series for
> > example).
>
> I'm a little stuck with this. :-/ I managed to prepare a new libcgi
> patch queue and got it correctly imported in
> platform-*/build-target/libcgi-1.0 where it is a git repository (ptxdist
> --git extract libcgi). Using git rebase -i and some cherry picking in my
> libcgi repo I got all the new patches there in the right order. I looked
> into opkg-utils as suggested and saw some tags on certain changesets in
> the temporary git repository, I also noticed the special markers in the
> series file of opkg-utils patch queue. What I thought was: just create
> similar tags, run `git ptx-patches` and you get those special markers.
> However this does not work. Sure the patches are created correctly, but
> the series file only contains the "ordinary" ptxdist magic without the
> tag stuff.
>
> How do I do this correctly? I'm afraid reading scripts/git-ptx-patches
> does not point me to the right thing.
It's a bit tricky. I usually do it like this:
1. Make one series without the special marker.
2. export the patches with ptx-patches
3. ptxdist clean <pkg>
4. edit the series and insert the marker with start numbers
5. ptxdist extract --git <pkg>
6. git ptx-patches -f -t <tag> for all tags
Now you should have the makers and patches with the correct numbering.
> btw: Due to your support over the last years, I'm able to get this far,
> using multiple branches, format-patch, send-email, rebase -i and this is
> awesome. Thanks for that.
You're welcome. You've submitted a lot of patches in return. So I think it
was well worth my time.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-24 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 9:19 Alexander Dahl
2014-03-19 9:49 ` Michael Olbrich
2014-03-19 10:28 ` Alexander Dahl
2014-03-21 13:35 ` Alexander Dahl
2014-03-24 8:41 ` Michael Olbrich [this message]
2014-04-02 14:10 ` [ptxdist] [PATCH] libcgi: " Alexander Dahl
2014-04-04 9:58 ` Michael Olbrich
2014-03-19 9:49 ` [ptxdist] [PATCH] " Alexander Dahl
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=20140324084153.GA10959@pengutronix.de \
--to=m.olbrich@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