From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2016, #03; Tue, 13)
Date: Tue, 13 Dec 2016 17:34:19 -0800 [thread overview]
Message-ID: <20161214013419.GA83860@google.com> (raw)
In-Reply-To: <xmqqd1gvz4x3.fsf@gitster.mtv.corp.google.com>
On 12/13, Junio C Hamano wrote:
> * bw/realpath-wo-chdir (2016-12-12) 4 commits
> - 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
>
> 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.
>
> What's the donness of the topic? Is this ready for 'next'?
Unless others have any additional comments I think it should be
ready for next.
> * bw/transport-protocol-policy (2016-12-05) 5 commits
> - transport: add from_user parameter to is_transport_allowed
> - http: create function to get curl allowed protocols
> - http: always warn if libcurl version is too old
> - transport: add protocol policy config option
> - lib-proto-disable: variable name fix
>
> Finer-grained control of what protocols are allowed for transports
> during clone/fetch/push have been enabled via a new configuration
> mechanism.
>
> What's the doneness of this topic? Did we agree that it should be
> rebased on top of Peff's http-walker-limit-redirect series?
Yes I believe we agreed it should be rebased on Peff's series. I can do
that and send out another version.
--
Brandon Williams
next prev parent reply other threads:[~2016-12-14 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 1:16 What's cooking in git.git (Dec 2016, #03; Tue, 13) Junio C Hamano
2016-12-14 1:34 ` Brandon Williams [this message]
2016-12-14 1:37 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161214013419.GA83860@google.com \
--to=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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).