git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #01; Fri, 2)
Date: Fri, 02 Feb 2024 21:22:36 -0800	[thread overview]
Message-ID: <xmqqzfwirujn.fsf@gitster.g> (raw)
In-Reply-To: <xmqqr0hutm1x.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 02 Feb 2024 16:43:06 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> * jk/diff-external-with-no-index (2024-01-29) 1 commit
>   (merged to 'next' on 2024-01-30 at 30c3e9f91d)
>  + diff: handle NULL meta-info when spawning external diff
>
>  "git diff --no-index file1 file2" segfaulted while invoking the
>  external diff driver, which has been corrected.
>
>  Reverted out of 'next' for now, seems to break "win test (n)" jobs.
>  cf. <xmqqh6irwtkd.fsf@gitster.g>
>  source: <20240129015708.GA1762343@coredump.intra.peff.net>

The above topic is marked as such by mistake.  It is on track to be
merged to 'master'.  What was temporarily reverted was the next one.

> * jk/unit-tests-buildfix (2024-01-31) 3 commits
>   (merged to 'next' on 2024-01-31 at 00df31c4c8)
>  + t/Makefile: get UNIT_TESTS list from C sources
>  + Makefile: remove UNIT_TEST_BIN directory with "make clean"
>  + Makefile: use mkdir_p_parent_template for UNIT_TEST_BIN
>
>  Build dependency around unit tests has been fixed.
>
>  Will merge to 'master'.
>  source: <20240130053714.GA165967@coredump.intra.peff.net>

But Dscho helped to fix the breakage on "win test (n)" jobs so it
has again been queued to 'next'.



      reply	other threads:[~2024-02-03  5:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03  0:43 What's cooking in git.git (Feb 2024, #01; Fri, 2) Junio C Hamano
2024-02-03  5:22 ` 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

  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=xmqqzfwirujn.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.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.
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).