xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH 1/2] mg-force-push: unshift . onto @INC
Date: Mon, 29 Jan 2018 17:29:06 +0000	[thread overview]
Message-ID: <1517246947-24154-1-git-send-email-ian.jackson@eu.citrix.com> (raw)

This script seems to have missed out on the bulk commit fixing this
problem.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 mg-force-push | 1 +
 1 file changed, 1 insertion(+)

diff --git a/mg-force-push b/mg-force-push
index 4a8f0a2..09c1894 100755
--- a/mg-force-push
+++ b/mg-force-push
@@ -10,6 +10,7 @@
 use strict;
 use warnings;
 
+BEGIN { unshift @INC, qw(.); }
 use Osstest;
 
 my @dryrun;
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2018-01-29 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 17:29 Ian Jackson [this message]
2018-01-29 17:29 ` [OSSTEST PATCH 2/2] mg-hosts: Call db_readonly_report inside, not outside, db_retry Ian Jackson

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=1517246947-24154-1-git-send-email-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).