Re: [PATCH v6 0/7] Trace env variables in run_command()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v6 0/7] Trace env variables in run_command()
From: Jeff King <peff@xxxxxxxx>
Date: Fri, 19 Jan 2018 16:39:44 -0500
Cc: git@xxxxxxxxxxxxxxx, Stefan Beller <sbeller@xxxxxxxxxx>, Brandon Williams <bmwill@xxxxxxxxxx>, Junio C Hamano <gitster@xxxxxxxxx>, Johannes Sixt <j6t@xxxxxxxx>
In-reply-to: <20180118094512.27849-1-pclouds@gmail.com>
References: <20180115105949.18328-1-pclouds@gmail.com> <20180118094512.27849-1-pclouds@gmail.com>

On Thu, Jan 18, 2018 at 04:45:05PM +0700, Nguyễn Thái Ngọc Duy wrote:

> v6 squashes Junio's changes in 6/7 and moves trace_run_command() from
> trace.c to run-command.c.

Thanks, this version looks good to me.

-Peff

References:
- [PATCH v5 0/7] Trace env variables in run_command()
  - From: Nguyễn Thái Ngọc Duy
- [PATCH v6 0/7] Trace env variables in run_command()
  - From: Nguyễn Thái Ngọc Duy

Prev by Date: Re: [PATCH v2 4/6] Force test suite traps to be cleared for NonStop ksh
Next by Date: Re: [PATCH] mru: Replace mru.[ch] with list.h implementation
Previous by thread: [PATCH v6 7/7] run-command.c: print new cwd in trace_run_command()
Next by thread: Re: [PATCH] run-command.c: print env vars when GIT_TRACE is set
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux