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.3
Date: Mon, 15 May 2006 21:49:50 -0700	[thread overview]
Message-ID: <7vk68mfua9.fsf@assigned-by-dhcp.cox.net> (raw)

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

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

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

This contains two notable non-fixes:

 (1) Future-proofing configuration file syntax by Linus.
     Nothing in 1.3.X series takes advantage of it, but it is
     there so 1.3.3 would not barf in a repository that you
     previously used later versions of git to manipulate its
     configuration file.

 (2) core.prefersymlinkrefs configuration can be set in the
     configuration file while bisecting a project that wants to
     use .git/HEAD symbolic link in its historical version
     (notably Linux kernel around January this year).

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

Changes since v1.3.2 are as follows:

Ben Clifford:
      include header to define uint32_t, necessary on Mac OS X

Dennis Stosberg:
      Fix git-pack-objects for 64-bit platforms
      Fix compilation on newer NetBSD systems

Dmitry V. Levin:
      Separate object name errors from usage errors

Eric Wong:
      apply: fix infinite loop with multiple patches with --index
      Install git-send-email by default

Johannes Schindelin:
      repo-config: trim white-space before comment

Junio C Hamano:
      core.prefersymlinkrefs: use symlinks for .git/HEAD
      repo-config: document what value_regexp does a bit more clearly.
      Fix repo-config set-multivar error return path.
      Documentation: {caret} fixes (git-rev-list.txt)
      checkout: use --aggressive when running a 3-way merge (-m).
      Fix pack-index issue on 64-bit platforms a bit more portably.

Linus Torvalds:
      Fix "git diff --stat" with long filenames
      revert/cherry-pick: use aggressive merge.
      git config syntax updates

Martin Waitz:
      clone: keep --reference even with -l -s
      repack: honor -d even when no new pack was created

Matthias Lederhofer:
      core-tutorial.txt: escape asterisk

Pavel Roskin:
      Release config lock if the regex is invalid

Sean Estabrooks:
      Fix for config file section parsing.
      Another config file parsing fix.
      Ensure author & committer before asking for commit message.

Yakov Lerner:
      read-cache.c: use xcalloc() not calloc()

                 reply	other threads:[~2006-05-16  4:49 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=7vk68mfua9.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