All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, bmwill@google.com
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2016, #08; Tue, 27)
Date: Thu, 29 Dec 2016 11:10:37 +0100	[thread overview]
Message-ID: <9E13F972-F374-4126-A599-A8A7618D4AF3@gmail.com> (raw)
In-Reply-To: <xmqqy3z155o1.fsf@gitster.mtv.corp.google.com>


> On 28 Dec 2016, at 00:11, Junio C Hamano <gitster@pobox.com> wrote:
> 
> 
> * bw/realpath-wo-chdir (2016-12-22) 5 commits
>  (merged to 'next' on 2016-12-22 at fea8fa870f)
> + real_path: canonicalize directory separators in root parts
> + real_path: have callers use real_pathdup and strbuf_realpath
> + real_path: create real_pathdup
> + real_path: convert real_path_internal to strbuf_realpath
> + real_path: resolve symlinks by hand
> (this branch is used by bw/grep-recurse-submodules.)
> 
> The implementation of "real_path()" was to go there with chdir(2)
> and call getcwd(3), but this obviously wouldn't be usable in a
> threaded environment.  Rewrite it to manually resolve relative
> paths including symbolic links in path components.

"real_path: resolve symlinks by hand" (05b458c) introduces
"MAXSYMLINKS" which is already defined on macOS in

/usr/include/sys/param.h:197:9:

 * .., MAXSYMLINKS defines the
 * maximum number of symbolic links that may be expanded in a path name.
 * It should be set high enough to allow all legitimate uses, but halt
 * infinite loops reasonably quickly.
 */


Log with JS: https://travis-ci.org/git/git/jobs/187092215
Log without JS: https://s3.amazonaws.com/archive.travis-ci.org/jobs/187092215/log.txt

- Lars


  parent reply	other threads:[~2016-12-29 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 23:11 What's cooking in git.git (Dec 2016, #08; Tue, 27) Junio C Hamano
2016-12-28 18:18 ` Brandon Williams
2016-12-29 10:06   ` Duy Nguyen
2017-01-03 12:20     ` Duy Nguyen
2017-01-03 17:58       ` Brandon Williams
2016-12-29 10:10 ` Lars Schneider [this message]
2017-01-03 18:54   ` Brandon Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9E13F972-F374-4126-A599-A8A7618D4AF3@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=bmwill@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.