From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2018, #02; Sat, 13)
Date: Fri, 12 Oct 2018 12:44:23 -0700 [thread overview]
Message-ID: <CAGZ79kZGEMWpr7aqeqXbC4bkmsCCiW+1pxbEV4T0vfsYG+_3iA@mail.gmail.com> (raw)
In-Reply-To: <xmqqh8hr9pxb.fsf@gitster-ct.c.googlers.com>
>
> * 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. <CAGZ79kbV6QjsFKcD2uG_P9j1AvzSNQSi-_jXGQ9w0YU9fjhEGg@mail.gmail.com>
I started rewriting the documentation according to your proposal of having
parameters with name, then referred to as NAME in the docs.
After a few examples, I must admit I do not like that style,
so I would just want to do the minimal part that would get this patch landed,
i.e.
(a) convince you that the patch is good as-is or
(b) resend with fewer parameters made explicit if
we desire to be concise instead.
> * nd/the-index (2018-09-21) 23 commits
> (merged to 'next' on 2018-10-10 at 16e2e2e947)
[...]
> (this branch is used by sb/more-repo-in-api.)
>
> Various codepaths in the core-ish part learn to work on an
> arbitrary in-core index structure, not necessarily the default
> instance "the_index".
>
> Will merge to 'master'.
Cool!
sb/more-repo-in-api is not part of this message,
but it requires at least one resend, so I'll do that.
> * 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 of in worktree
> . repository: repo_submodule_init to take a submodule struct
> . submodule.c: do not copy around submodule list
> . submodule.c: move global changed_submodule_names into fetch submodule struct
> . submodule.c: sort changed_submodule_names before searching it
> . submodule.c: fix indentation
> . sha1-array: provide oid_array_filter
>
> "git fetch --recurse-submodules" may not fetch the necessary commit
> that is bound to the superproject, which is getting corrected.
>
> Ejected for now, as it has fallouts in places like t/helper/.
This is the first time I hear about that, I'll look into that.
The tipmost commit there is also shoddy, I'll redo that.
next prev parent reply other threads:[~2018-10-12 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 14:53 What's cooking in git.git (Oct 2018, #02; Sat, 13) Junio C Hamano
2018-10-12 15:02 ` Ævar Arnfjörð Bjarmason
2018-10-12 19:44 ` Stefan Beller [this message]
2018-10-12 23:37 ` Stefan Beller
2018-10-13 1:03 ` Junio C Hamano
2018-10-15 17:32 ` Stefan Beller
2018-10-16 21:20 ` Josh Steadmon
2018-10-16 23:11 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kZGEMWpr7aqeqXbC4bkmsCCiW+1pxbEV4T0vfsYG+_3iA@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).