public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] List of patches that failed to apply to 4.4-stable
Date: Mon, 19 Nov 2018 16:31:39 +0000	[thread overview]
Message-ID: <2102685.09LOIKHG4k@linux-if6s> (raw)
In-Reply-To: <000901d47d73$eadf22b0$c09d6810$@toshiba.co.jp>

Hi,

On Friday, 16 November 2018 06:16:31 WET Daniel Sangorrin wrote:
> To kernel team,
> 
> @SZLin: thanks for creating a page on the wiki just for that.
> 
> Yesterday, I checked the patches in my "failed to apply to 4.4-stable" list against the actual git repository using a short python script.
> It turns out that some of the patches in the "to apply" list were already there applied.
> 
> I have updated our wiki page accordingly
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4-failed-patches
> 
> For the curious minds, you can find my (dirty) script attached to this e-mail.

If you can put the patches list as a repo on gitlab, and since the target repo is already being mirrored, I wonder if we can create a job that executes the script when the origin list gets updated. We can create a notification with the outcome to our testing mailing list. This way we just need to focus on having the origin in shape. If we add to this a way to parser the outcome in .md format and published as result in gitlab when the job "succeeds", we significantly reduce the effort associated to the wiki page.

@Daniel W. is the above possible, based on your experience with Gitlab?

Best Regards


-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy.   See https://www.codethink.co.uk/privacy.html

  reply	other threads:[~2018-11-19 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  9:15 [cip-dev] List of patches that failed to apply to 4.4-stable Daniel Sangorrin
2018-11-12 11:03 ` SZ Lin (林上智)
2018-11-16  6:16   ` Daniel Sangorrin
2018-11-19 16:31     ` Agustín Benito Bethencourt [this message]
2018-11-19 16:53       ` Daniel Wagner
2018-11-19 17:24         ` Agustín Benito Bethencourt

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=2102685.09LOIKHG4k@linux-if6s \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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