Josh Steadmon writes:
> The first two patches (test cleanup and packet_reader refactor) are OK,
> but the latter two will break the archive command when an old client
> attempts to talk to a new server (due to the version advertisement
> problem noted in [1]). Sorry that I didn't catch that
On 2018.10.12 23:53, Junio C Hamano wrote:
> * js/remote-archive-v2 (2018-09-28) 4 commits
> (merged to 'next' on 2018-10-12 at 5f34377f60)
> + archive: allow archive over HTTP(S) with proto v2
> + archive: implement protocol v2 archive command
> + archive: use packet_reader for
On Fri, Oct 12, 2018 at 6:03 PM Junio C Hamano wrote:
>
> Stefan Beller writes:
>
> >> * sb/submodule-recursive-fetch-gets-the-tip (2018-10-11) 9 commits
> >> . builtin/fetch: check for submodule updates for non branch fetches
> >> . fetch: retry fetching submodules if needed objects were not
Stefan Beller writes:
>> * sb/submodule-recursive-fetch-gets-the-tip (2018-10-11) 9 commits
>> . builtin/fetch: check for submodule updates for non branch fetches
>> . fetch: retry fetching submodules if needed objects were not fetched
>> . submodule: fetch in submodules git directory instead
On Fri, Oct 12, 2018 at 12:44 PM Stefan Beller wrote:
> > * sb/submodule-recursive-fetch-gets-the-tip (2018-10-11) 9 commits
> > . builtin/fetch: check for submodule updates for non branch fetches
> > . fetch: retry fetching submodules if needed objects were not fetched
> > . submodule: fetch
>
> * sb/strbuf-h-update (2018-09-29) 1 commit
> - strbuf.h: format according to coding guidelines
>
> Code clean-up to serve as a BCP example.
>
> What's the status of this one after the discussion thread stopped here?
> cf.
I started rewriting the documentation according to your proposal
On Fri, Oct 12 2018, Junio C Hamano wrote:
> * ab/gc-doc-update (2018-10-11) 1 commit
> - gc doc: mention the commit-graph in the intro
>
> The documentation of "git gc" has been updated to mention that it
> is no longer limited to "pruning away crufts" but also updates
> ancillary files
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.
Quite a lot of topics have been
8 matches
Mail list logo
