Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Leonardo Sandoval <leonardo.sandoval.gonzalez@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for "liberation-fonts: update to 2...." and 4 more
Date: Thu, 4 May 2017 10:32:19 +0000	[thread overview]
Message-ID: <07ec7ed100e14d63bc17945084522fdd@XBOX02.axis.com> (raw)
In-Reply-To: <6447df1b-8742-7451-1978-68527f141437@linux.intel.com>

> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Alexander Kanavin
> Sent: den 4 maj 2017 12:17
> To: Paul Eggleton <paul.eggleton@linux.intel.com>
> Cc: Leonardo Sandoval <leonardo.sandoval.gonzalez@intel.com>;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] ✗ patchtest: failure for "liberation-fonts:
> update to 2...." and 4 more
> 
> On 05/04/2017 01:07 PM, Paul Eggleton wrote:
> > The original idea was that the tests could also be run from your
> local machine
> > (could easily be as a git hook), and whilst it's not as easy as I
> might have
> > liked it is doable - however even if it were much easier, we have to
> be
> > realistic and acknowledge that most people still won't do it.
> 
> I thought default git hooks can be enforced by the remote repo when you
> do a clone, no?

Nope, standard Git has no such support. It would be a security risk if 
the remote repository would provide hooks that started running on the 
client without being actively activated.

> Alex

//Peter


  reply	other threads:[~2017-05-04 10:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 13:11 [PATCH 1/5] liberation-fonts: update to 2.00.1 Alexander Kanavin
2017-05-03 13:11 ` [PATCH 2/5] packagegroup-core-lsb: do not include Qt4 anymore Alexander Kanavin
2017-05-03 13:11 ` [PATCH 3/5] libpng12: remove the recipe Alexander Kanavin
2017-05-03 18:41   ` Max Krummenacher
2017-05-03 18:58     ` Burton, Ross
2017-05-04  9:18       ` Alexander Kanavin
2017-05-04  9:54         ` Burton, Ross
2017-05-04 23:48           ` Max Krummenacher
2017-05-05  9:16             ` Alexander Kanavin
2017-05-07 23:46               ` Paul Eggleton
2017-05-05 10:10             ` Burton, Ross
2017-05-03 13:11 ` [PATCH 4/5] recipes-lsb4/perl: remove the recipes Alexander Kanavin
2017-05-04 10:49   ` Richard Purdie
2017-05-04 10:54     ` Alexander Kanavin
2017-05-04 11:16       ` Richard Purdie
2017-05-03 13:11 ` [PATCH 5/5] mailx: remove the recipe Alexander Kanavin
2017-05-03 13:31 ` ✗ patchtest: failure for "liberation-fonts: update to 2...." and 4 more Patchwork
2017-05-03 21:43   ` Paul Eggleton
2017-05-04  9:33     ` Alexander Kanavin
2017-05-04 10:07       ` Paul Eggleton
2017-05-04 10:16         ` Alexander Kanavin
2017-05-04 10:32           ` Peter Kjellerstedt [this message]
2017-05-04 10:32           ` Paul Eggleton
2017-05-04 15:36         ` Leonardo Sandoval

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=07ec7ed100e14d63bc17945084522fdd@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=leonardo.sandoval.gonzalez@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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