From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] dbus: update the recipes to 1.10.0
Date: Thu, 27 Aug 2015 14:45:43 +0300 [thread overview]
Message-ID: <55DEF867.3020500@linux.intel.com> (raw)
In-Reply-To: <55DEF697.5010106@collabora.co.uk>
On 08/27/2015 02:37 PM, Andrew Shadura wrote:
> On 27/08/15 13:22, Jussi Kukkonen wrote:
>> Could you please configure your git so that it tries harder to find
>> renames: it's hard to see the changes otherwise. Something like this
>> would work in git config (the other option is renames=copies):
>
> Right, thanks for the suggestion. Resubmitting that patch.
Whenever you change something else than the version number and tarball
checksums (e.g. build options, or dependencies, or adding/removing
patches), it's good to explain in the commit log message what was
updated and why. So you provide answers to the 'why' questions before
people ask them :)
Regards,
Alex
next prev parent reply other threads:[~2015-08-27 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 9:12 [PATCH 1/3] dbus: merge .bb and .inc Andrew Shadura
2015-08-27 9:12 ` [PATCH 2/3] dbus: update the recipes to 1.10.0 Andrew Shadura
2015-08-27 11:22 ` Jussi Kukkonen
2015-08-27 11:37 ` Andrew Shadura
2015-08-27 11:45 ` Alexander Kanavin [this message]
2015-08-27 9:12 ` [PATCH 3/3] dbus: add apparmor support Andrew Shadura
2015-08-28 3:53 ` [PATCH 1/3] dbus: merge .bb and .inc Khem Raj
2015-08-28 12:22 ` Andrew Shadura
2015-08-28 14:23 ` Khem Raj
2015-08-28 14:25 ` Andrew Shadura
2015-08-28 12:56 ` Andrew Shadura
2015-08-28 14:24 ` Khem Raj
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=55DEF867.3020500@linux.intel.com \
--to=alexander.kanavin@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.