From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] lib/oe/patch.py: add a warning if patch context was ignored
Date: Thu, 15 Mar 2018 18:22:38 +0200 [thread overview]
Message-ID: <f6229a05-c425-6da9-aac2-026cdcbed92a@linux.intel.com> (raw)
In-Reply-To: <CA+chaQctko3eBUWpySaiZ19WXH+5cDrAu4Kh6TGLd9r4MTx-Qw@mail.gmail.com>
On 03/15/2018 05:13 PM, Martin Jansa wrote:
> Now when more people will use devtool to refresh patches, would it make
> sense for devtool to use --no-signature when refreshing patches?
I don't think that will help much to reduce the amount of change in the
refresh. The refesh will also update the line numbers in chunks so that
they match reality, and convert patches into git format - all useful things.
Alex
next prev parent reply other threads:[~2018-03-15 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 16:49 [PATCH 1/4] package.bbclass: run pre/post installation/removal scriptlets using sh -e Alexander Kanavin
2018-03-12 16:49 ` [PATCH 2/4] meta/lib/oe/package_manager.py: warn about failing scriptlets for all package types Alexander Kanavin
2018-03-12 16:49 ` [PATCH 3/4] oe-selftest: add a test for failing package post-installation scriptlets Alexander Kanavin
2018-03-12 16:49 ` [PATCH 4/4] lib/oe/patch.py: add a warning if patch context was ignored Alexander Kanavin
2018-03-15 15:13 ` Martin Jansa
2018-03-15 16:22 ` Alexander Kanavin [this message]
2018-03-15 16:41 ` Martin Jansa
2018-03-15 16:46 ` Alexander Kanavin
2018-03-15 18:38 ` 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=f6229a05-c425-6da9-aac2-026cdcbed92a@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.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.