From: Junio C Hamano <gitster@pobox.com>
To: David Turner <novalis@novalis.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2021, #04; Tue, 10)
Date: Wed, 11 Aug 2021 12:00:20 -0700 [thread overview]
Message-ID: <xmqqk0kr958b.fsf@gitster.g> (raw)
In-Reply-To: <0C7D8DD1-C26A-4E04-BAAA-A63BF1017142@novalis.org> (David Turner's message of "Wed, 11 Aug 2021 13:49:08 -0400")
David Turner <novalis@novalis.org> writes:
> On August 10, 2021 9:12:41 PM EDT, Junio C Hamano <gitster@pobox.com> wrote:
>>Here are the topics that have been cooking in my tree.
>>...
>>* dt/submodule-diff-fixes (2021-08-02) 3 commits
>> - diff --submodule=diff: Don't print failure message twice
>> - diff --submodule=diff: do not fail on ever-initialied deleted submodules
>> - t4060: remove unused variable
>>
>> "git diff --submodule=diff" showed failure from run_command() when
>> trying to run diff inside a submodule, when the user manually
>> removes the submodule directory.
>>
>> Seems to break CI when merged to 'seen'
>> cf. https://github.com/git/git/runs/3259477809?check_suite_focus=true#step:4:2618
>
> That link says "Merge branch 'fs/ssh-signing' into seen" -- that's not my branch.
That one was for 913a4aa7e46 which had not just fs/ssh-signing but also
dt/submodule-diff-fixes; near its tip there are:
913a4aa7e4 Merge branch 'fs/ssh-signing' into seen
c9787deb45 Merge branch 'ab/only-single-progress-at-once' into seen
a3a4793406 Merge branch 'ab/lib-subtest' into seen
cb170c8941 Merge branch 'jh/builtin-fsmonitor' into seen
4eaca15257 Merge branch 'cf/fetch-set-upstream-while-detached' into seen
fc20552335 Merge branch 'tb/multi-pack-bitmaps' into seen
f6758f313b Merge branch 'dt/submodule-diff-fixes' into seen
c29c5aa324 Merge branch 'ab/make-tags-cleanup' into seen
ca277e7504 Merge branch 'ab/fsck-unexpected-type' into seen
a2c57f0aca Merge branch 'ab/config-based-hooks-base' into seen
f586246edb Merge branch 'ab/serve-cleanup' into seen
f55b1792d9 Merge branch 'es/superproject-aware-submodules' into seen
prev parent reply other threads:[~2021-08-11 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 1:12 What's cooking in git.git (Aug 2021, #04; Tue, 10) Junio C Hamano
2021-08-11 1:34 ` brian m. carlson
2021-08-11 7:22 ` Fabian Stelzer
2021-08-11 8:04 ` Carlo Marcelo Arenas Belón
2021-08-11 16:13 ` Junio C Hamano
2021-08-11 9:51 ` Phillip Wood
2021-08-11 16:19 ` Junio C Hamano
2021-08-13 8:10 ` ZheNing Hu
2021-08-11 10:45 ` Atharva Raykar
2021-08-11 17:30 ` Junio C Hamano
2021-08-11 12:21 ` Patrick Steinhardt
2021-08-11 16:44 ` Junio C Hamano
2021-08-11 17:49 ` David Turner
2021-08-11 19:00 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk0kr958b.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=novalis@novalis.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.