From: Martin Jansa <martin.jansa@gmail.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for initramfs-framework installation improvements (rev4)
Date: Mon, 4 Dec 2017 21:26:02 +0100 [thread overview]
Message-ID: <20171204202602.GA4220@jama> (raw)
In-Reply-To: <20171204092359.0bef0632@lsandov1-mobl2.zpn.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3079 bytes --]
On Mon, Dec 04, 2017 at 09:23:59AM -0600, Leonardo Sandoval wrote:
> On Fri, 1 Dec 2017 23:07:48 +0100
> Martin Jansa <martin.jansa@gmail.com> wrote:
>
> > Is it trying to apply whole series (including the 2 patches which were
> > already merged to master and actually introduced the issue I was trying to
> > fix)?
> >
> > Does it mean that I cannot send a fix into the e-mail thread where the
> > issue was introduced and discussed?
>
> I do not the answer but I can tell you about the fail check: patchtest is pretty dummy in this check, it simply does git apply --check <your series.mbox> so you need to base on master's HEAD.
But the patch I've sent is rebased on master's HEAD.
My question is how to send the patch to the thread where it IMHO belongs
without patchtest trying to apply all the patches in the thread (if
that's what it meants by "series".
See:
https://patchwork.openembedded.org/series/9783/
the last patch isn't 3/3 from this series, it's just independent new fix for changes
introduced in this series (e-mail thread).
so it should apply only this one:
https://patchwork.openembedded.org/patch/146352/
I know this cannot be as clever as e.g. gerrit, but my question still
stands:
Do we need to send fixes for already merged changes as new e-mail
threads (replace In-reply-to: with maybe just a link to ML archive
in the commit message)?
Regards,
> > On Fri, Dec 1, 2017 at 11:02 PM, Patchwork <
> > patchwork@patchwork.openembedded.org> wrote:
> >
> > > == Series Details ==
> > >
> > > Series: initramfs-framework installation improvements (rev4)
> > > Revision: 4
> > > URL : https://patchwork.openembedded.org/series/9783/
> > > State : failure
> > >
> > > == Summary ==
> > >
> > >
> > > Thank you for submitting this patch series to OpenEmbedded Core. This is
> > > an automated response. Several tests have been executed on the proposed
> > > series by patchtest resulting in the following failures:
> > >
> > >
> > >
> > > * Issue Series does not apply on top of target branch
> > > [test_series_merge_on_head]
> > > Suggested fix Rebase your series on top of targeted branch
> > > Targeted branch master (currently at addf309165)
> > >
> > >
> > >
> > > If you believe any of these test results are incorrect, please reply to the
> > > mailing list (openembedded-core@lists.openembedded.org) raising your
> > > concerns.
> > > Otherwise we would appreciate you correcting the issues and submitting a
> > > new
> > > version of the patchset if applicable. Please ensure you add/increment the
> > > version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
> > > [PATCH v3] -> ...).
> > >
> > > ---
> > > Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_
> > > Guidelines
> > > Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> > > Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
> > >
> > >
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
prev parent reply other threads:[~2017-12-04 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 21:20 [PATCH 0/3] initramfs-framework installation improvements California Sullivan
2017-11-14 21:20 ` [PATCH 1/3] initramfs-module-install-efi: point to original copy and delete new file California Sullivan
2017-11-15 20:31 ` Otavio Salvador
2017-11-14 21:20 ` [PATCH 2/3] initramfs-module-install-efi: update summary California Sullivan
2017-11-15 20:31 ` Otavio Salvador
2017-11-14 21:20 ` [PATCH 3/3] initramfs-framework: add install module California Sullivan
2017-11-14 22:03 ` [PATCH 3/3 V2] " California Sullivan
2017-12-01 21:01 ` Martin Jansa
2017-12-01 21:53 ` [PATCH] initramfs-module-install: Remove allarch and FILESEXTRAPATHS Martin Jansa
2017-12-07 18:13 ` Cal Sullivan
2017-12-01 22:05 ` [PATCH 3/3 V2] initramfs-framework: add install module Cal Sullivan
2017-11-14 22:10 ` [PATCHi 3/3 V3] " California Sullivan
2017-11-15 20:36 ` Otavio Salvador
2017-12-01 22:02 ` ✗ patchtest: failure for initramfs-framework installation improvements (rev4) Patchwork
2017-12-01 22:07 ` Martin Jansa
2017-12-04 15:23 ` Leonardo Sandoval
2017-12-04 20:26 ` Martin Jansa [this message]
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=20171204202602.GA4220@jama \
--to=martin.jansa@gmail.com \
--cc=leonardo.sandoval.gonzalez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox