xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: [PATCH v8 0/6] xen: systemd support
Date: Wed, 30 Jul 2014 18:43:38 +0200	[thread overview]
Message-ID: <20140730164338.GW21930@wotan.suse.de> (raw)
In-Reply-To: <1406737540.29218.1.camel@kazak.uk.xensource.com>

On Wed, Jul 30, 2014 at 05:25:40PM +0100, Ian Campbell wrote:
> On Wed, 2014-07-30 at 18:22 +0200, Luis R. Rodriguez wrote:
> 
> > > Also, you should probably invoke the script with $(BASH), else IIRC you
> > > will break *BSD (where bash is in ports not /bin)
> 
> > This is a Linux script though,
> 
> True.
> 
> >  I'll use  #!/usr/bin/env bash
> > instead then.
> 
> That's worse than either $(BASH) or a normal #! IMHO.

Do you mean to call $BASH foo.sh on the makefile ?
On Linux we can run scripts often on Makefiles with
either #!/bin/bash or the env thing just fine. I've
never actually have seen the use of $(BASH) foo.sh
within the Makefile. I promise to address issues
if found with this approach.

  Luis

  reply	other threads:[~2014-07-30 16:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26  2:14 [PATCH v8 0/6] xen: systemd support Luis R. Rodriguez
2014-07-26  2:14 ` [PATCH v8 1/6] cxenstored: also fail if only 1 socket was given by systemd Luis R. Rodriguez
2014-07-26  2:14 ` [PATCH v8 2/6] oxenstored: " Luis R. Rodriguez
2014-07-26  2:14 ` [PATCH v8 3/6] autoconf: xen: move standard path variables to config/Paths.mk.in Luis R. Rodriguez
2014-08-04 14:24   ` Julien Grall
2014-08-04 14:28     ` Ian Campbell
2014-08-04 14:30   ` Ian Campbell
2014-09-23  7:55     ` Luis R. Rodriguez
2014-09-23  8:15       ` Olaf Hering
2014-09-23  8:19         ` Luis R. Rodriguez
2014-07-26  2:14 ` [PATCH v8 4/6] xencommons: move module list into a generic place Luis R. Rodriguez
2014-07-26  2:14 ` [PATCH v8 5/6] autoconf: xen: enable explicit preference option for xenstored preference Luis R. Rodriguez
2014-07-26  2:14 ` [PATCH v8 6/6] systemd: add xen systemd service and module files Luis R. Rodriguez
2014-07-28 12:46 ` [PATCH v8 0/6] xen: systemd support Ian Campbell
2014-07-28 15:02   ` Luis R. Rodriguez
2014-07-28 15:05     ` Ian Campbell
2014-07-28 17:57       ` Luis R. Rodriguez
2014-07-29  8:56         ` Ian Campbell
2014-07-30 16:22           ` Luis R. Rodriguez
2014-07-30 16:25             ` Ian Campbell
2014-07-30 16:43               ` Luis R. Rodriguez [this message]
2014-07-31  8:30                 ` Ian Campbell
2014-07-28 16:52   ` Andrew Cooper
2014-07-28 16:57     ` Andrew Cooper
2014-07-28 17:00       ` Luis R. Rodriguez
2014-07-28 18:33         ` Luis R. Rodriguez
2014-07-29  8:54           ` Ian Campbell
2014-07-29  9:33             ` Andrew Cooper
2014-07-29  9:49               ` Ian Campbell
2014-07-29 10:47                 ` Andrew Cooper

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=20140730164338.GW21930@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=mcgrof@do-not-panic.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).