Re: What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-09-02 Thread Stephen & Linda Smith
On Wednesday, August 29, 2018 3:35:57 PM MST Junio C Hamano wrote: > > * mk/use-size-t-in-zlib (2017-08-10) 1 commit > . zlib.c: use size_t for size > > The wrapper to call into zlib followed our long tradition to use > "unsigned long" for sizes of regions in memory, which have been >

Re: What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-08-31 Thread Kaartic Sivaraam
On 30 August 2018 21:41:35 GMT+05:30, Elijah Newren wrote: >That makes sense. I'm not sure I can concisely convey all the right >points, but here's a stab at rewording: > >Recent addition of "directory rename" heuristics to the >merge-recursive backend makes the command susceptible to false

Re: What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-08-31 Thread Junio C Hamano
Elijah Newren writes: >> Suggestions for a better rewrite is very much appreciated. > > That makes sense. I'm not sure I can concisely convey all the right > points, but here's a stab at rewording: > > Recent addition of "directory rename" heuristics to the > merge-recursive backend makes the

Re: What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-08-30 Thread Elijah Newren
On Thu, Aug 30, 2018 at 8:44 AM Junio C Hamano wrote: > > Elijah Newren writes: > > >> Recent addition of "directory rename" heuristics to the > >> merge-recursive backend makes the command susceptible to false > >> positives and false negatives, but the risk is even more grave when > >>

Re: What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-08-30 Thread Junio C Hamano
Elijah Newren writes: >> Recent addition of "directory rename" heuristics to the >> merge-recursive backend makes the command susceptible to false >> positives and false negatives, but the risk is even more grave when >> used in the context of "git am -3", which does not know about any >>

es/format-patch-{inter,range}diff, was Re: What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-08-30 Thread Johannes Schindelin
Hi Junio, On Wed, 29 Aug 2018, Junio C Hamano wrote: > * es/format-patch-interdiff (2018-07-23) 6 commits > - format-patch: allow --interdiff to apply to a lone-patch > - log-tree: show_log: make commentary block delimiting reusable > - interdiff: teach show_interdiff() to indent interdiff >

What's cooking in git.git (Aug 2018, #06; Wed, 29)

2018-08-29 Thread 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 branches, but I am still holding onto them. Git 2.19-rc1 is out. Hopefully