From: Patrick Ohly <patrick.ohly@intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: using devtool for rebasing patches
Date: Thu, 03 Nov 2016 17:52:50 +0100 [thread overview]
Message-ID: <1478191970.13356.103.camel@intel.com> (raw)
In-Reply-To: <6511599a-ddb1-77b0-f42e-69afeaa60cae@linux.intel.com>
On Thu, 2016-11-03 at 18:01 +0200, Alexander Kanavin wrote:
> Hello Paul,
>
> it would be very useful if devtool offered support for rebasing source
> patches when they fail to apply
+1 for that.
I tried it the other way around: first "devtool modify", then rebasing
using git (which only works when the recipe fetches from a git repo),
and finally changing the recipe such that it refers to the version I
rebased onto. But that version change in the recipe confused "devtool
update-recipe" considerably (as in "added all patches between the
version", if I remember correctly).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-11-03 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 16:01 using devtool for rebasing patches Alexander Kanavin
2016-11-03 16:29 ` Christopher Larson
2016-11-03 16:35 ` Alexander Kanavin
2016-11-03 17:14 ` Christopher Larson
2016-11-03 19:14 ` Patrick Ohly
2016-11-03 19:24 ` Paul Eggleton
2016-11-03 19:27 ` Khem Raj
2016-11-03 16:52 ` Patrick Ohly [this message]
2016-11-03 19:29 ` Paul Eggleton
2016-11-03 19:34 ` Paul Eggleton
2016-11-04 13:54 ` Alexander Kanavin
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=1478191970.13356.103.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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