RE: [PATCH 2/2] t: use test_config whenever possible

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

Subject: RE: [PATCH 2/2] t: use test_config whenever possible
From: Firmin Martin <firminmartin24@xxxxxxxxx>
Date: Sun, 16 May 2021 00:00:29 +0200
Cc: Junio C Hamano <gitster@xxxxxxxxx>
In-reply-to: <60a02d62838cf_eacf5208d2@natae.notmuch>
References: <20210514065508.247044-1-firminmartin24@gmail.com> <20210514065508.247044-2-firminmartin24@gmail.com> <60a02bf2f16a2_eacf52085@natae.notmuch> <60a02d62838cf_eacf5208d2@natae.notmuch>

>
> Ahh, I just read the comment about not using it in a subshell.
>
> Then outside:
>
>   test_config -C downstream fetch.recurseSubmodules on-demand &&
True. This makes me realize that I should also briefly document the -C option.

Thanks,

Firmin

References:
- [PATCH 1/2] t/README: document test_config
  - From: Firmin Martin
- [PATCH 2/2] t: use test_config whenever possible
  - From: Firmin Martin
- RE: [PATCH 2/2] t: use test_config whenever possible
  - From: Felipe Contreras
- RE: [PATCH 2/2] t: use test_config whenever possible
  - From: Felipe Contreras

Prev by Date: RE: [PATCH 2/2] t: use test_config whenever possible
Next by Date: Man pages have colors? A deep dive into groff
Previous by thread: RE: [PATCH 2/2] t: use test_config whenever possible
Next by thread: Re: [PATCH 1/2] t/README: document test_config
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