On Mon, Aug 15, 2016 at 1:36 PM, Junio C Hamano wrote:
>
>>> Why do you need "err_buf", instead of directly writing the error to
>>> "err", especially if "err" is not optional?
>>>
+ ...
+out:
+ if (err_buf.len) {
>>
>> If we were directly writing to err, we
Stefan Beller writes:
> On Fri, Aug 12, 2016 at 3:25 PM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> + struct strbuf sb = STRBUF_INIT;
>>> + char *ref_git = compute_alternate_path(item->string, );
>>
>> Who owns the
On Fri, Aug 12, 2016 at 3:25 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> + struct strbuf sb = STRBUF_INIT;
>> + char *ref_git = compute_alternate_path(item->string, );
>
> Who owns the memory for ref_git?
The caller of
Stefan Beller writes:
> + struct strbuf sb = STRBUF_INIT;
> + char *ref_git = compute_alternate_path(item->string, );
Who owns the memory for ref_git?
> - if (!access(mkpath("%s/shallow", ref_git), F_OK))
> - die(_("reference repository '%s' is
4 matches
Mail list logo