git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.5.2.5
Date: Wed, 15 Aug 2007 16:24:16 -0700	[thread overview]
Message-ID: <7vr6m4mlen.fsf@gitster.siamese.dyndns.org> (raw)

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

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

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

Although 1.5.3 has been in -rc cycle for quite some time, there
was a rather nasty data corruption bug discovered, so here is
primarily to push that fix out.

When "git add -u $paths" records ONLY removes in a directory,
your next "git write-tree" will write out a bogus tree object
and cause your commit not to match the reality.


GIT v1.5.2.5 Release Notes
==========================

Fixes since v1.5.2.4
--------------------

 * Bugfixes

   - "git add -u" had a serious data corruption problem in one
     special case (when the changes to a subdirectory's files
     consist only deletion of files).

   - "git add -u <path>" did not work from a subdirectory.

   - "git apply" left an empty directory after all its files are
     renamed away.

   - "git $anycmd foo/bar", when there is a file 'foo' in the
     working tree, complained that "git $anycmd foo/bar --" form
     should be used to disambiguate between revs and files,
     which was completely bogus.

   - "git checkout-index" and other commands that checks out
     files to the work tree tried unlink(2) on directories,
     which is a sane thing to do on sane systems, but not on
     Solaris when you are root.

 * Documentation Fixes and Updates

   - A handful documentation fixes.

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

Changes since v1.5.2.4 are as follows:

Christian Couder (1):
      rev-list --bisect: fix allocation of "int*" instead of "int".

Julian Phillips (1):
      Force listingblocks to be monospaced in manpages

Junio C Hamano (4):
      Do not expect unlink(2) to fail on a directory.
      setup.c:verify_non_filename(): don't die unnecessarily while disambiguating
      Fix "git add -u" data corruption.
      GIT 1.5.2.5

Linus Torvalds (1):
      apply: remove directory that becomes empty by renaming the last file away

Salikh Zakirov (1):
      git-add -u paths... now works from subdirectory

                 reply	other threads:[~2007-08-15 23:24 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=7vr6m4mlen.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.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 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).