Re: [PATCHv6 1/4] Read (but not write) from $XDG_CONFIG_HOME/git/config file
- From
Ramsay Jones <ramsay@ramsay1.demon.co.uk>
- Date
- Jun 12, 2012, 17:42 UTC
- Message-ID
- <4FD77F9A.6060202@ramsay1.demon.co.uk>
- In-Reply-To
- <20120608115711.Horde.-kmJPHwdC4BP0cx3RNFDX2A@webmail.minatec.grenoble-inp.fr>
nguyenhu@minatec.inpg.fr wrote:
Show 20 quoted lines
> Junio C Hamano <gitster@pobox.com> a écrit :
>
>>> +char *mkpathdup(const char *fmt, ...)
>>> +{
>>> + char path[PATH_MAX];
>>> + va_list args;
>>> + unsigned len;
>>> +
>>> + va_start(args, fmt);
>>> + len = vsnprintf(path, sizeof(path), fmt, args);
>>> + va_end(args);
>>> + if (len >= sizeof(path))
>>> + return xstrdup(bad_path);
>>> + return xstrdup(cleanup_path(path));
>>> +}
>> Hrmph. If a new helper is introduced anyway, wouldn't it be a better
>> idea to get rid of the hardcoded PATH_MAX limitation, perhaps using
>> strbuf_vaddf() or something in the implementation of this function?
>
> Ramsay Jones, what do you think about this ?I think that I'm sorry for the late reply, I've been away ... :-D
I noticed your new series (v7 I think) which looked good (as far as the mkpathdup() implementation is concerned) and I don't think it will tickle the cygwin bug. (I haven't actually fetched that mail yet, I've only read it using my ISPs web-mail interface, but will do so soon and test it on cygwin).
Thanks!
ATB, Ramsay Jones