All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git v2.46.2
Date: Mon, 23 Sep 2024 14:02:39 -0700	[thread overview]
Message-ID: <xmqqa5fyytg0.fsf@gitster.g> (raw)

The latest maintenance release Git v2.46.2 is now available at
the usual places.

The tarballs are found at:

    https://www.kernel.org/pub/software/scm/git/

The following public repositories all have a copy of the 'v2.46.2'
tag and the 'maint' branch that the tag points at:

  url = https://git.kernel.org/pub/scm/git/git
  url = https://kernel.googlesource.com/pub/scm/git/git
  url = git://repo.or.cz/alt-git.git
  url = https://github.com/gitster/git

----------------------------------------------------------------
Git 2.46.2 Release Notes
========================

This release is primarily to merge changes to unbreak the 32-bit
GitHub actions jobs we use for CI testing, so that we can release
real fixes for the 2.46.x track after they pass CI.

It also reverts the "git patch-id" change that went into 2.46.1,
as it seems to have got a regression reported (I haven't verified,
but it is better to keep a known breakage than adding an unintended
regression).

Other than that, a handful of minor bugfixes are included.

 * In a few corner cases "git diff --exit-code" failed to report
   "changes" (e.g., renamed without any content change), which has
   been corrected.

 * Cygwin does have /dev/tty support that is needed by things like
   single-key input mode.

 * The interpret-trailers command failed to recognise the end of the
   message when the commit log ends in an incomplete line.

----------------------------------------------------------------

Changes since v2.46.1 are as follows:

Brian Lyles (1):
      interpret-trailers: handle message without trailing newline

Jeff King (4):
      ci: drop run-docker scripts
      ci: unify ubuntu and ubuntu32 dependencies
      ci: use more recent linux32 image
      ci: use regular action versions for linux32 job

Junio C Hamano (5):
      doc: remote.*.skip{DefaultUpdate,FetchAll} stops prefetch
      ci: remove 'Upload failed tests' directories' step from linux32 jobs
      Revert "Merge branch 'jc/patch-id' into maint-2.46"
      Start preparing for Git 2.46.2
      Git 2.46.2

Martin Ågren (2):
      t1517: add missing LIBCURL prereq
      t0211: add missing LIBCURL prereq

Patrick Steinhardt (1):
      ci: add Ubuntu 16.04 job to GitLab CI

Ramsay Jones (1):
      config.mak.uname: add HAVE_DEV_TTY to cygwin config section

René Scharfe (2):
      diff: report copies and renames as changes in run_diff_cmd()
      diff: report dirty submodules as changes in builtin_diff()


                 reply	other threads:[~2024-09-23 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=xmqqa5fyytg0.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@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.
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.