Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Junio C Hamano
Junio C Hamano writes: > The tip of 'next' hasn't been rewound yet, but the states of many > topics that were marked to "Cook in 'next'" read "Will merge to > 'master'" now. I'll probably start merging a handful of topics that > have been in 'next' down to 'master' tonight (they appear at the >

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Junio C Hamano
Derrick Stolee writes: >> Replaced with a newer version. > > I think this has been the same note for a few weeks now. What does it > mean? Did I send a new version out that you haven't picked up? It just means that I didn't bother to look at the current status message for the topic that had

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Derrick Stolee
On 9/14/2018 5:56 PM, Junio C Hamano wrote: * ds/format-commit-graph-docs (2018-08-21) 2 commits - commit-graph.txt: improve formatting for asciidoc - Docs: Add commit-graph tech docs to Makefile Design docs for the commit-graph machinery is now made into HTML as well as text. Will

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Jonathan Nieder
Jeff King wrote: > Let me inject some more uncertainty, then. ;) > > If we are not going to do 3/3, then should 2/3 simply avoid passing "-1" > back via return from main? I guess I don't have a strong opinion, but > one of the things I noted was that we converted those die() calls > introduced in

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Jeff King
On Mon, Sep 17, 2018 at 10:51:35AM -0700, Junio C Hamano wrote: > Jeff King writes: > > >> > What's the donness of this one? > >> > cf. <20180717201348.gd26...@sigill.intra.peff.net> > >> > >> This topic has stayed in 'pu' for a long time. I thought it was > >> concluded that this was a good

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Junio C Hamano
Jeff King writes: >> > What's the donness of this one? >> > cf. <20180717201348.gd26...@sigill.intra.peff.net> >> >> This topic has stayed in 'pu' for a long time. I thought it was >> concluded that this was a good change? Jeff, Jonathan? > > I read over the thread again. I don't think I

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Junio C Hamano
Antonio Ospite writes: > I did send a v4 addressing this: > https://public-inbox.org/git/20180824132951.8000-1-...@ao2.it/ > > In case you missed it I might as well send a v5 with some minor > cosmetic touches suggested by Ævar: > https://public-inbox.org/git/87wosfesxl@evledraar.gmail.com/

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-17 Thread Junio C Hamano
"brian m. carlson" writes: > On Fri, Sep 14, 2018 at 02:56:36PM -0700, Junio C Hamano wrote: >> * bc/hash-independent-tests (2018-09-13) 12 commits >> - t5318: use test_oid for HASH_LEN >> - t1407: make hash size independent >> - t1406: make hash-size independent >> - t1405: make hash size

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-16 Thread Jeff King
On Sun, Sep 16, 2018 at 08:39:03AM +0200, Duy Nguyen wrote: > On Fri, Sep 14, 2018 at 11:56 PM Junio C Hamano wrote: > > * jn/gc-auto (2018-07-17) 3 commits > > - gc: do not return error for prior errors in daemonized mode > > - gc: exit with status 128 on failure > > - gc: improve handling

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-16 Thread Ævar Arnfjörð Bjarmason
On Sun, Sep 16 2018, Duy Nguyen wrote: > On Fri, Sep 14, 2018 at 11:56 PM Junio C Hamano wrote: >> * jn/gc-auto (2018-07-17) 3 commits >> - gc: do not return error for prior errors in daemonized mode >> - gc: exit with status 128 on failure >> - gc: improve handling of errors reading gc.log

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-16 Thread brian m. carlson
On Fri, Sep 14, 2018 at 02:56:36PM -0700, Junio C Hamano wrote: > * bc/hash-independent-tests (2018-09-13) 12 commits > - t5318: use test_oid for HASH_LEN > - t1407: make hash size independent > - t1406: make hash-size independent > - t1405: make hash size independent > - t1400: switch

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-16 Thread Duy Nguyen
On Fri, Sep 14, 2018 at 11:56 PM Junio C Hamano wrote: > * jn/gc-auto (2018-07-17) 3 commits > - gc: do not return error for prior errors in daemonized mode > - gc: exit with status 128 on failure > - gc: improve handling of errors reading gc.log > > "gc --auto" ended up calling exit(-1) upon

Re: What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-15 Thread Antonio Ospite
On Fri, 14 Sep 2018 14:56:36 -0700 Junio C Hamano wrote: [...] > * ao/submodule-wo-gitmodules-checked-out (2018-08-14) 7 commits > - submodule: support reading .gitmodules even when it's not checked out > - t7506: clean up .gitmodules properly before setting up new scenario > - submodule: use

What's cooking in git.git (Sep 2018, #03; Fri, 14)

2018-09-14 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. The tip of 'next' hasn't been