Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "Maxin B. John" <maxin.john@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] piglit: upgrade to current git master
Date: Tue, 27 Feb 2018 15:23:32 +0000	[thread overview]
Message-ID: <3bfe61278db543eebcf07e019f5dd758@XBOX02.axis.com> (raw)
In-Reply-To: <1519735027-10472-2-git-send-email-maxin.john@intel.com>

> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Maxin B. John
> Sent: den 27 februari 2018 13:37
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 2/3] piglit: upgrade to current git master
> 
> Upgrade to revision:
> 4ce0887e2f7f848d2be2e435a2d0f3c80e44ea3b
> 
> remove backported patch:
>         0001-tests-egl-egl-context-priority.c-Use-piglit_egl_get_.patch
> 
> Signed-off-by: Maxin B. John <maxin.john@intel.com>
> 
> i# Your branch is ahead of 'origin/master' by 2 commits.
  ^
I guess that was an accidental key press turning the comment into 
an actual part of the commit message. ;)

> Signed-off-by: Maxin B. John <maxin.john@intel.com>

//Peter


  reply	other threads:[~2018-02-27 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 12:37 [PATCH 1/3] libinput: upgrade to version 1.10.0 Maxin B. John
2018-02-27 12:37 ` [PATCH 2/3] piglit: upgrade to current git master Maxin B. John
2018-02-27 15:23   ` Peter Kjellerstedt [this message]
2018-02-27 15:35     ` Maxin B. John
2018-02-27 12:37 ` [PATCH 3/3] puzzles: upgrade to latest revision Maxin B. John
2018-02-27 13:05 ` ✗ patchtest: failure for "libinput: upgrade to version 1..." and 2 more (rev2) Patchwork

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=3bfe61278db543eebcf07e019f5dd758@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=maxin.john@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