From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] strace: update to 4.7
Date: Thu, 14 Jun 2012 12:30:27 -0700 [thread overview]
Message-ID: <4FDA3BD3.1090300@linux.intel.com> (raw)
In-Reply-To: <1339701258.24333.98.camel@ted>
On 06/14/2012 12:14 PM, Richard Purdie wrote:
> On Thu, 2012-06-14 at 11:57 -0700, Saul Wold wrote:
>> On 06/12/2012 12:59 AM, Bogdan Marinescu wrote:
>>> Removed the x32 specific patches, since they seem to be fully
>>> integrated into 4.7. Also removed the sigmask patch, since the
>>> new version doesn't seem to use sigmask anymore.
>>>
>>> Signed-off-by: Bogdan Marinescu<bogdan.a.marinescu@intel.com>
>>> ---
>>> .../strace/strace-4.6/sigmask.patch | 23 -
>>> .../strace-4.6/strace-4.6_add_x32_support.patch | 1242 --------------------
>>> meta/recipes-devtools/strace/strace_4.6.bb | 23 -
>>> meta/recipes-devtools/strace/strace_4.7.bb | 20 +
>>> 4 files changed, 20 insertions(+), 1288 deletions(-)
>>> delete mode 100644 meta/recipes-devtools/strace/strace-4.6/sigmask.patch
>>> delete mode 100644 meta/recipes-devtools/strace/strace-4.6/strace-4.6_add_x32_support.patch
>>> delete mode 100644 meta/recipes-devtools/strace/strace_4.6.bb
>>> create mode 100644 meta/recipes-devtools/strace/strace_4.7.bb
>>>
>> Did you do a git mv? by removing and creating, the git history gets
>> lost, can you respin this?
>
> This is an urban myth. git does not track renames, ever. Some of the
> tools can detect and display things with "rename detection" though.
>
> So the patch was just sent without rename detection, it will make no
> difference to the history whatsoever if merged. It can be harder to
> review though. Rename detection doesn't always work in the cases of
> large delta, the exact threshold can be configured.
>
If that's the case, then this passed the rest of my testing also can
could be included in the C-Pull, I just dropped, I will pull it back in,
but not update the main request.
Sau!
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-06-14 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 7:59 [PATCH] strace: update to 4.7 Bogdan Marinescu
2012-06-12 13:59 ` Khem Raj
2012-06-12 15:13 ` Marinescu, Bogdan A
2012-06-12 15:25 ` Paul Eggleton
2012-06-12 15:31 ` Robert P. J. Day
2012-06-12 16:05 ` Paul Eggleton
2012-06-12 15:35 ` Marinescu, Bogdan A
2012-06-14 12:42 ` Marinescu, Bogdan A
2012-06-14 21:27 ` Khem Raj
2012-06-15 7:42 ` Marinescu, Bogdan A
2012-06-15 12:24 ` Richard Purdie
2012-06-14 18:57 ` Saul Wold
2012-06-14 19:14 ` Richard Purdie
2012-06-14 19:30 ` Saul Wold [this message]
2012-06-15 18:10 ` Saul Wold
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=4FDA3BD3.1090300@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.