Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Taylor Blau writes: > For now, the Message-ID that I was referring to is: > 20180410001826.GB67209@syl.local. [1] Thanks.

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

On Mon, Apr 23, 2018 at 08:33:11AM +0900, Junio C Hamano wrote: > Taylor Blau writes: > > > I noticed that tb/config-default, however, only landed two commits: > > > > - builtin/config: introduce `color` type specifier > > - config.c: introduce 'git_config_color' to parse

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Taylor Blau writes: > I noticed that tb/config-default, however, only landed two commits: > > - builtin/config: introduce `color` type specifier > - config.c: introduce 'git_config_color' to parse ANSI colors > > but not: > > - builtin/config: introduce `--default`

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

On Tue, Apr 17, 2018 at 03:07:46PM +0900, Junio C Hamano wrote: > * tb/config-type (2018-04-10) 2 commits > - builtin/config.c: support `--type=` as preferred alias for `--` > - builtin/config.c: treat type specifiers singularly > (this branch is used by tb/config-default.) > > The "git

js/rebase-recreate-merges, was Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Hi Junio, On Tue, 17 Apr 2018, Junio C Hamano wrote: > * js/rebase-recreate-merge (2018-04-11) 15 commits > - rebase -i --rebase-merges: add a section to the man page > - rebase -i: introduce --rebase-merges=[no-]rebase-cousins > - pull: accept --rebase=merges to recreate the branch topology

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Junio C Hamano writes: [...] > > * js/rebase-recreate-merge (2018-04-11) 15 commits [...] > "git rebase" learned "--rebase-merges" to transplant the whole > topology of commit graph elsewhere. > > This looked more or less ready for 'next'. Please stop me if there > are

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Elijah Newren writes: > On Mon, Apr 16, 2018 at 11:07 PM, Junio C Hamano wrote: >> * en/rename-directory-detection-reboot (2018-04-16) 32 commits >> ... >> - directory rename detection: testcases to avoid taking detection too far >> - directory rename

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Christian Hesse writes: > Junio C Hamano on Tue, 2018/04/17 15:07: >> * ab/simplify-perl-makefile (2018-04-11) 1 commit >> (merged to 'next' on 2018-04-17 at 4448756934) >> + perl: fix installing modules from contrib >> >> Recent simplification of build

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Jonathan Tan writes: >> I considered this done a long time ago, >> >> "All 6 patches look good to me, thanks. >> Reviewed-by: Jonathan Tan " >> >> https://public-inbox.org/git/20180328161727.af10f596dffc8e01205c4...@google.com/ > > To

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Derrick Stolee writes: > I'm sorry that my second message was terse. My response to v1 [1] was > >> I looked through these patches and only found one set of whitespace >> > > errors. Compiles and tests fine on my machine. > > Reviewed-by: > Derrick Stolee

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

On Mon, Apr 16, 2018 at 11:07 PM, Junio C Hamano wrote: > * en/rename-directory-detection-reboot (2018-04-16) 32 commits > - merge-recursive: fix check for skipability of working tree updates > - merge-recursive: Fix was_tracked() to quit lying with some renamed paths > -

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Junio C Hamano on Tue, 2018/04/17 15:07: > * ab/simplify-perl-makefile (2018-04-11) 1 commit > (merged to 'next' on 2018-04-17 at 4448756934) > + perl: fix installing modules from contrib > > Recent simplification of build procedure forgot a bit of tweak to > the build

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

On Tue, Apr 17, 2018 at 11:05 AM, Stefan Beller wrote: >> * sb/submodule-move-nested (2018-03-29) 6 commits >> - submodule: fixup nested submodules after moving the submodule >> - submodule-config: remove submodule_from_cache >> - submodule-config: add repository argument

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

On 4/17/2018 9:04 PM, Junio C Hamano wrote: Stefan Beller writes: What's the doneness of this thing? I didn't recall seeing any response, especially ones that demonstrated the reviewer carefully read and thought about the issues surrounding the code. Not that I

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Stefan Beller writes: >> What's the doneness of this thing? I didn't recall seeing any >> response, especially ones that demonstrated the reviewer carefully >> read and thought about the issues surrounding the code. Not that I >> spotted any problems in these patches

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

Hi Junio, > -- > [New Topics] > * sb/object-store-replace (2018-04-12) 15 commits ... > The effort to pass the repository in-core structure throughout the > API continues. This round deals with the code that implements the > refs/replace/

Re: What's cooking in git.git (Apr 2018, #02; Tue, 17)

On Tue, Apr 17, 2018 at 2:07 AM, Junio C Hamano wrote: > * so/grossary-ancestor (2018-04-17) 1 commit > - glossary: substitute "ancestor" for "direct ancestor" in 'push' > description. s/grossary/glossary/

What's cooking in git.git (Apr 2018, #02; Tue, 17)

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. I try to summarize what each