Re: What's cooking in git.git (Apr 2017, #01; Tue, 11)
- Date: Tue, 11 Apr 2017 12:12:05 +0200
- From: Christian Couder <christian.couder@xxxxxxxxx>
- Subject: Re: What's cooking in git.git (Apr 2017, #01; Tue, 11)
> * cc/split-index-config (2017-03-30) 1 commit
> - read-cache: avoid using git_path() in freshen_shared_index()
> The split-index code configuration code used an unsafe git_path()
> function without copying its result out.
> Needs to be explained better.
> The code looked OK, though.
it looked like you were ok with the explanation or you actually wanted
it to be shorter.
So should I send a shorter one? Or should I add explanation about why
git_path() is unsafe?