On Wed, May 07, 2014 at 02:33:27PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:25:06PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > In a normal torture-test run, the script inherits its environment
> > variables, but this does not work when producing a
On Mon, Apr 28, 2014 at 05:25:06PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> In a normal torture-test run, the script inherits its environment
> variables, but this does not work when producing a script that is
> to run later. Therefore, definitions and exports are prepended
On Mon, Apr 28, 2014 at 05:25:06PM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
In a normal torture-test run, the script inherits its environment
variables, but this does not work when producing a script that is
to run later. Therefore, definitions and
On Wed, May 07, 2014 at 02:33:27PM -0700, j...@joshtriplett.org wrote:
On Mon, Apr 28, 2014 at 05:25:06PM -0700, Paul E. McKenney wrote:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
In a normal torture-test run, the script inherits its environment
variables, but this does not work
From: "Paul E. McKenney"
In a normal torture-test run, the script inherits its environment
variables, but this does not work when producing a script that is
to run later. Therefore, definitions and exports are prepended to
a dryrun script but not to a script that is run immediately. This
From: Paul E. McKenney paul...@linux.vnet.ibm.com
In a normal torture-test run, the script inherits its environment
variables, but this does not work when producing a script that is
to run later. Therefore, definitions and exports are prepended to
a dryrun script but not to a script that is run
6 matches
Mail list logo