Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

Jeff King writes: > On Wed, Jun 15, 2016 at 09:35:20AM +0200, Elia Pinto wrote: > >> > * ep/http-curl-trace (2016-05-24) 2 commits >> > - imap-send.c: introduce the GIT_TRACE_CURL enviroment variable >> > - http.c: implement the GIT_TRACE_CURL environment variable >> > >> >

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

On Wed, Jun 15, 2016 at 09:35:20AM +0200, Elia Pinto wrote: > > * ep/http-curl-trace (2016-05-24) 2 commits > > - imap-send.c: introduce the GIT_TRACE_CURL enviroment variable > > - http.c: implement the GIT_TRACE_CURL environment variable > > > > HTTP transport gained an option to produce

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

On Wed, Jun 15, 2016 at 11:32:39AM -0700, Junio C Hamano wrote: > Mike Hommey writes: > > > On Tue, Jun 14, 2016 at 03:08:04PM -0700, Junio C Hamano wrote: > > >> * mh/connect (2016-06-06) 10 commits > >> - connect: [host:port] is legacy for ssh > >> ... > >> - connect:

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

Duy Nguyen writes: >> * nd/worktree-cleanup-post-head-protection (2016-05-24) 6 commits >> - worktree: simplify prefixing paths >> - worktree: avoid 0{40}, too many zeroes, hard to read >> - worktree.c: use is_dot_or_dotdot() >> - git-worktree.txt: keep subcommand listing

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

Mike Hommey writes: > On Tue, Jun 14, 2016 at 03:08:04PM -0700, Junio C Hamano wrote: >> * mh/connect (2016-06-06) 10 commits >> - connect: [host:port] is legacy for ssh >> ... >> - connect: document why we sometimes call get_port after get_host_and_port >> >> Ok, folks,

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

On Wed, Jun 15, 2016 at 5:08 AM, Junio C Hamano wrote: > * nd/i-t-a-commitable (2016-06-06) 3 commits > - commit: don't count i-t-a entries when checking if the new commit is empty > - Resurrect "diff-lib.c: adjust position of i-t-a entries in diff" > - diff.h: extend

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

2016-06-15 0:08 GMT+02:00 Junio C Hamano : > Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. The ones marked with '.' do not appear in any of > the integration

Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)

On Tue, Jun 14, 2016 at 03:08:04PM -0700, Junio C Hamano wrote: > Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. The ones marked with '.' do not appear in any of > the integration

What's cooking in git.git (Jun 2016, #04; Tue, 14)

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. Git 2.9 has been tagged. Let's