From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)
Date: Mon, 21 Nov 2022 12:36:36 +0900 [thread overview]
Message-ID: <xmqqpmdhx9kr.fsf@gitster.g> (raw)
In-Reply-To: <Y3q9xrq5u9YSuVQC@nand.local> (Taylor Blau's message of "Sun, 20 Nov 2022 18:52:38 -0500")
Taylor Blau <me@ttaylorr.com> writes:
> On Mon, Nov 21, 2022 at 08:24:21AM +0900, Junio C Hamano wrote:
>> Taylor Blau <me@ttaylorr.com> writes:
>>
>> > * ab/various-leak-fixes (2022-11-08) 18 commits
>> > (merged to 'next' on 2022-11-18 at 8828bb7161)
>> > ...
>> > (this branch is used by ab/merge-index-prep.)
>>
>> > * pw/rebase-no-reflog-action (2022-11-09) 2 commits
>> > (merged to 'next' on 2022-11-14 at 790dadc8d3)
>> > ...
>> > (this branch is used by ab/merge-index-prep.)
>>
>> The other topic referred to is not described anywhere, and not part
>> of 'seen'. Intended?
>
> It was merged intentionally via 790dadc8d3 (Merge branch
> 'pw/rebase-no-reflog-action' into next, 2022-11-14) as you note, though
> I'm not sure why the description from 790dadc8d3 didn't make it into the
> WC report.
>
> In any case, the description I went with is:
>
> Avoid setting GIT_REFLOG_ACTION to improve readability of the
> sequencer internals.
Sorry, but the question was about ab/merge-index-prep that does not
exist in the report and not in 'seen'.
For now, I'll ignore that phantom user of these two topics. It can
come back when dust settles ;-).
next prev parent reply other threads:[~2022-11-21 3:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 2:22 What's cooking in git.git (Nov 2022, #04; Fri, 18) Taylor Blau
2022-11-20 11:24 ` SZEDER Gábor
2022-11-20 17:42 ` Looking for a review (pretty-formats, hard truncation), was What's cooking in git.git (Nov 2022, #04; Fri, 18)) Philip Oakley
2022-11-21 0:37 ` Junio C Hamano
2022-11-21 18:10 ` Philip Oakley
2022-11-20 19:46 ` What's cooking in git.git (Nov 2022, #04; Fri, 18) Phillip Wood
2022-11-20 21:24 ` Johannes Schindelin
2022-11-21 0:47 ` Junio C Hamano
2022-11-21 1:00 ` Taylor Blau
2022-11-22 14:58 ` Phillip Wood
2022-11-20 21:45 ` Junio C Hamano
2022-11-20 23:51 ` Taylor Blau
2022-11-20 23:24 ` Junio C Hamano
2022-11-20 23:52 ` Taylor Blau
2022-11-21 3:36 ` Junio C Hamano [this message]
2022-11-22 22:56 ` Taylor Blau
2022-11-21 0:10 ` Junio C Hamano
2022-11-21 0:16 ` Taylor Blau
2022-11-23 0:03 ` Junio C Hamano
2022-11-21 22:22 ` ab/submodule-no-abspath (was Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)) Glen Choo
2022-11-22 22:45 ` [PATCH] submodule absorbgitdirs: use relative <from> and <to> paths Ævar Arnfjörð Bjarmason
2022-11-23 0:43 ` Glen Choo
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=xmqqpmdhx9kr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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).