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.3.2
Date: Thu, 04 May 2006 01:01:28 -0700	[thread overview]
Message-ID: <7v4q066wx3.fsf@assigned-by-dhcp.cox.net> (raw)

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

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

	git-1.3.2.tar.{gz,bz2}			(tarball)
	RPMS/$arch/git-*-1.3.2-1.$arch.rpm	(RPM)

Mostly documentation and usability fixes, with no exciting new
features, as the maintenance series ought to be.

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

Changes since v1.3.1 are as follows:

Huw Davies:
      git-format-patch: Use rfc2822 compliant date.

Jon Loeliger:
      Alphabetize the glossary.
      Added definitions for a few words:
      Add a few more words to the glossary.

Junio C Hamano:
      rebase: typofix.
      commit-tree.c: check_valid() microoptimization.
      verify-pack: check integrity in a saner order.
      git-am --resolved: more usable error message.

Linus Torvalds:
      Fix filename verification when in a subdirectory

Martin Langhoff:
      git-send-email: fix version string to be valid perl

Matthias Kestenholz:
      annotate: fix warning about uninitialized scalar
      annotate: display usage information if no filename was given
      fix various typos in documentation

Robert Shearman:
      give "what now" hint to users upon git-am failure.

Sean Estabrooks:
      Update the git-branch man page to include the "-r" option,
      Fix up remaining man pages that use asciidoc "callouts".
      Properly render asciidoc "callouts" in git man pages.
      Fix trivial typo in git-log man page.

                 reply	other threads:[~2006-05-04  8:01 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=7v4q066wx3.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