threads / announce / 27256

[ANNOUNCE] Git 1.7.5.1

Subject: [ANNOUNCE] Git 1.7.5.1

## tl;dr

3 messages between May 5, 2011 and May 5, 2011.

replies: 2people: 3as markdown or json

Junio C Hamano· May 5, 2011, 01:35 UTC · lore

The latest maintenance release Git 1.7.5.1 is available at the usual places:

  http://www.kernel.org/pub/software/scm/git/
  git-1.7.5.1.tar.{gz,bz2}			(source tarball)
  git-htmldocs-1.7.5.1.tar.{gz,bz2}		(preformatted docs)
  git-manpages-1.7.5.1.tar.{gz,bz2}		(preformatted docs)
The RPM binary packages for a few architectures are found in:
  RPMS/$arch/git-*-1.7.5.1-1.fc13.$arch.rpm	(RPM)

Git v1.7.5.1 Release Notes ==========================

Fixes since v1.7.5 ------------------

 * When an object "$tree:$path" does not exist, if $path does exist in the
   subtree of $tree that corresponds to the subdirectory the user is in,
   git now suggests using "$tree:./$path" in addition to the advice to use
   the full path from the root of the working tree.
 * The "--date=relative" output format used to say "X years, 12 months"
   when it should have said "X+1 years".
 * The smart-HTTP transfer was broken in 1.7.5 when the client needs
   to issue a small POST (which uses content-length) and then a large
   POST (which uses chunked) back to back.
 * "git clean" used to fail on an empty directory that is not readable,
   even though rmdir(2) could remove such a directory.  Now we attempt it
   as the last resort.
 * The "--dirstat" option of "diff" family of commands used to totally
   ignore a change that only rearranged lines within a file.  Such a
   change now counts as at least a minimum but non zero change.
 * The "--dirstat" option of "diff" family of commands used to use the
   pathname in the original, instead of the pathname in the result,
   when renames are involved.
 * "git pack-object" did not take core.bigfilethreashold into account
   (unlike fast-import); now it does.
 * "git reflog" ignored options like "--format=.." on the command line.
 * "git stash apply" used to refuse to work if there was any change in
   the working tree, even when the change did not overlap with the change
   the stash recorded.
 * "git stash apply @{99999}" was not diagnosed as an error, even when you
   did not have that many stash entries.
 * An error message from "git send-email" to diagnose a broken SMTP
   connection configuration lacked a space between "hello=<smtp-domain>"
   and "port=<smtp-server-port>".
And other minor fixes and documentation updates.
----------------------------------------------------------------
Changes since v1.7.5 are as follows:
Alex Riesen (1):
      clean: unreadable directory may still be rmdir-able if it is empty
Dan McGee (2):
      stash: add two more tests for --no-keep-index
      stash: ensure --no-keep-index and --patch can be used in any order
Jeff King (3):
      stash: fix accidental apply of non-existent stashes
      stash: drop dirty worktree check on apply
      upload-pack: start pack-objects before async rev-list
Johan Herland (4):
      --dirstat: Describe non-obvious differences relative to --stat or regular diff
      --dirstat-by-file: Make it faster and more correct
      Teach --dirstat not to completely ignore rearranged lines within a file
      --dirstat: In case of renames, use target filename instead of source filename
Jon Seymour (1):
      stash: fix false positive in the invalid ref test.
Junio C Hamano (4):
      Teach core.bigfilethreashold to pack-objects
      http: clear POSTFIELDS when initializing a slot
      Start 1.7.5.1 maintenance track
      Git 1.7.5.1
Michael J Gruber (6):
      builtin/log.c: separate default and setup of cmd_log_init()
      t/t1411: test reflog with formats
      reflog: fix overriding of command line options
      t1506: factor out test for "Did you mean..."
      sha1_name: Suggest commit:./file for path in subdir
      date: avoid "X years, 12 months" in relative dates
Sylvain Rabot (1):
      git-send-email: fix missing space in error message
Valentin Haenel (1):
      git-add.txt: document 'add.ignoreErrors'
Sverre Rabbelier· May 5, 2011, 11:13 UTC · re: Junio C Hamano · lore

Re: [ANNOUNCE] Git 1.7.5.1

Heya,
On Thu, May 5, 2011 at 03:35, Junio C Hamano <gitster@pobox.com> wrote:
>  * "git stash apply" used to refuse to work if there was any change in
>   the working tree, even when the change did not overlap with the change
>   the stash recorded.

Does this mean that I won't get the "you have unstaged changes, please add them" message anymore for the non-overlapping case? If so, nice!

-- 
Cheers,

Sverre Rabbelier
Piotr Krukowiecki· May 5, 2011, 17:40 UTC · re: Sverre Rabbelier · lore

Re: [ANNOUNCE] Git 1.7.5.1

On Thu, May 5, 2011 at 1:13 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
Show 9 quoted lines
> Heya,
>
> On Thu, May 5, 2011 at 03:35, Junio C Hamano <gitster@pobox.com> wrote:
>>  * "git stash apply" used to refuse to work if there was any change in
>>   the working tree, even when the change did not overlap with the change
>>   the stash recorded.
>
> Does this mean that I won't get the "you have unstaged changes, please
> add them" message anymore for the non-overlapping case? If so, nice!

I think this also partially fixes problem with git-svn and concurrency described here: http://article.gmane.org/gmane.comp.version-control.git/171481

git-svn now works correctly if during dcommit someone else made a change to svn repository but the change did not touch dcommited file.

It still stops and looses history if change was in the same file.
Thanks,
-- 
Piotr Krukowiecki

← back to recent threads