archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
Cc: Linux Kernel <>,
Subject: [ANNOUNCE] Git v2.29.1
Date: Fri, 23 Oct 2020 07:30:22 -0700	[thread overview]
Message-ID: <> (raw)

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

The change in this release affects only those who build from the
source *and* install with a non-standard SKIP_DASHED_BUILT_INS
option turned on.  With the option turned on, Git 2.29 forgot to
install a few programs in /usr/bin that made it unusable as the
server side to accept pushes and fetches.

To everybody else, this release is irrelevant and ignorable.  We
know about at least one other brown-paper-bag regression we are
going to fix with another maintenance release, so it may be a better
idea to wait for 2.29.2 for most people.

The tarballs are found at:

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

  url =
  url = git://
  url =


Git v2.29.1 Release Notes

This is to fix the build procedure change in 2.29 where we failed
to install a few programs that should be installed in /usr/bin
(namely, receive-pack, upload-archive and upload-pack) when the
non-default SKIP_DASHED_BUILT_INS installation option is in effect.

A minor glitch in a non-default installation may usually not deserve
a hotfix, but I think Git for Windows ship binaries built with this
option, so let's make an exception.


Changes since v2.29.0 are as follows:

Johannes Schindelin (1):
      SKIP_DASHED_BUILT_INS: do not skip the bin/ programs

Junio C Hamano (1):
      Git 2.29.1

                 reply	other threads:[~2020-10-23 14:30 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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 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 NNTP newsgroup(s).