From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] Style issue for recipes
Date: Thu, 04 Sep 2014 13:03:41 -0700 [thread overview]
Message-ID: <5408C59D.7070706@gmail.com> (raw)
In-Reply-To: <CAJTo0LZYDn2vZt49Sj40W3GJ7RLiTZjVs8OjbrEU-2NBoTdyOQ@mail.gmail.com>
On 09/04/2014 09:26 AM, Burton, Ross wrote:
> On 4 September 2014 16:41, akuster808 <akuster808@gmail.com> wrote:
>> This is the same reason why I have split a bb into two parts when I submit
>> upgrades. I feel it makes reviewing easier the next time a package gets
>> upgraded. Trying to find the actual changes between a file being deleted and
>> the new one being added might lead to missing something.
>>
>> If there are unintentional consequence by doing this, that is a problem.
>
> This is what git format-patch -M is for: it detects the rename and
> shows a "proper" diff.
>
Ah, that is what -M does. That negates my concern.
thanks for the info.
- Armin
> Ross
>
next prev parent reply other threads:[~2014-09-04 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 14:12 Style issue for recipes Burton, Ross
2014-09-04 15:03 ` [oe] " Robert Yang
2014-09-04 15:41 ` akuster808
2014-09-04 16:26 ` Burton, Ross
2014-09-04 20:03 ` akuster808 [this message]
2014-09-04 16:07 ` Enrico Scholz
2014-09-04 16:29 ` Burton, Ross
2014-09-04 16:44 ` Peter A. Bigot
2014-09-04 17:00 ` Enrico Scholz
2014-09-04 17:38 ` Andreas Müller
2014-09-04 18:36 ` Enrico Scholz
2014-09-04 19:12 ` Burton, Ross
2014-09-29 0:51 ` Trevor Woerner
2014-09-04 16:34 ` Burton, Ross
2014-09-05 9:11 ` [oe] " Paul Eggleton
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=5408C59D.7070706@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox