Re: [PATCH v5 0/4] Per-worktree config file support

2017-01-19 Thread Stefan Beller
On Thu, Jan 19, 2017 at 4:09 AM, Duy Nguyen wrote: > On Wed, Jan 11, 2017 at 12:01 AM, Stefan Beller wrote: >> On Tue, Jan 10, 2017 at 3:25 AM, Nguyễn Thái Ngọc Duy >> wrote: >>> Let's get this rolling again. To refresh your memory because it's half >>> a year since v4 [1], this is about lettin

Re: [PATCH v5 0/4] Per-worktree config file support

2017-01-19 Thread Duy Nguyen
On Wed, Jan 11, 2017 at 12:01 AM, Stefan Beller wrote: > On Tue, Jan 10, 2017 at 3:25 AM, Nguyễn Thái Ngọc Duy > wrote: >> Let's get this rolling again. To refresh your memory because it's half >> a year since v4 [1], this is about letting each worktree in multi >> worktree setup has their own c

Re: [PATCH v5 0/4] Per-worktree config file support

2017-01-10 Thread Stefan Beller
On Tue, Jan 10, 2017 at 3:25 AM, Nguyễn Thái Ngọc Duy wrote: > Let's get this rolling again. To refresh your memory because it's half > a year since v4 [1], this is about letting each worktree in multi > worktree setup has their own config settings. The most prominent ones > are core.worktree, use

Re: [PATCH v5 0/4] Per-worktree config file support

2017-01-10 Thread Duy Nguyen
On Tue, Jan 10, 2017 at 6:25 PM, Nguyễn Thái Ngọc Duy wrote: > Not much has changed from v4, except that the migration to new config > layout is done automatically _update_ a config variable with "git > config --worktree". I accidentally two words that may make it hard to understand this sentence

[PATCH v5 0/4] Per-worktree config file support

2017-01-10 Thread Nguyễn Thái Ngọc Duy
Let's get this rolling again. To refresh your memory because it's half a year since v4 [1], this is about letting each worktree in multi worktree setup has their own config settings. The most prominent ones are core.worktree, used by submodules, and core.sparseCheckout. This time I'm not touching