Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.4.2.2
Date: Fri, 29 Sep 2006 23:53:41 -0700	[thread overview]
Message-ID: <7v8xk1j156.fsf@assigned-by-dhcp.cox.net> (raw)

The latest maintenance release GIT 1.4.2.2 is available at the
usual places:

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

  git-1.4.2.2.tar.{gz,bz2}			(tarball)
  git-htmldocs-1.4.2.2.tar.{gz,bz2}		(preformatted docs)
  git-manpages-1.4.2.2.tar.{gz,bz2}		(preformatted docs)
  RPMS/$arch/git-*-1.4.2.2-1.$arch.rpm	(RPM)

This is strictly a bugfix release.  While we will soon be in
stabilization slow-down for 1.4.3, one of the bugs this release
contains fixes for actually has bitten people who use the kernel
commits mailing list, so this is to push the fixes out early.

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

Changes since v1.4.2.1 are as follows:

Junio C Hamano:
      Fix git-am safety checks
      git-diff -B output fix.

Liu Yubao:
      Fix duplicate xmalloc in builtin-add

                 reply	other threads:[~2006-09-30  6:53 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=7v8xk1j156.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox