From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.5.1.1
Date: Wed, 11 Apr 2007 19:09:34 -0700 [thread overview]
Message-ID: <7vhcrml4wx.fsf@assigned-by-dhcp.cox.net> (raw)
The latest maintenance release GIT 1.5.1.1 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.1.1.tar.{gz,bz2} (tarball)
git-htmldocs-1.5.1.1.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.1.1.tar.{gz,bz2} (preformatted docs)
RPMS/$arch/git-*-1.5.1.1-1.$arch.rpm (RPM)
GIT v1.5.1.1 Release Notes
==========================
Fixes since v1.5.1
------------------
* Documentation updates
- The --left-right option of rev-list and friends is documented.
- The documentation for cvsimport has been majorly improved.
- "git-show-ref --exclude-existing" was documented.
* Bugfixes
- The implementation of -p option in "git cvsexportcommit" had
the meaning of -C (context reduction) option wrong, and
loosened the context requirements when it was told to be
strict.
- "git cvsserver" did not behave like the real cvsserver when
client side removed a file from the working tree without
doing anything else on the path. In such a case, it should
restore it from the checked out revision.
- "git fsck" issued an alarming error message on detached
HEAD. It is not an error since at least 1.5.0.
- "git send-email" produced of References header of unbounded length;
fixed this with line-folding.
- "git archive" to download from remote site should not
require you to be in a git repository, but it incorrectly
did.
- "git apply" ignored -p<n> for "diff --git" formatted
patches.
- "git rerere" recorded a conflict that had one side empty
(the other side adds) incorrectly; this made merging in the
other direction fail to use previously recorded resolution.
- t4200 test was broken where "wc -l" pads its output with
spaces.
- "git branch -m old new" to rename branch did not work
without a configuration file in ".git/config".
- The sample hook for notification e-mail was misnamed.
- gitweb did not show type-changing patch correctly in the
blobdiff view.
- git-svn did not error out with incorrect command line options.
- git-svn fell into an infinite loop when insanely long commit
message was found.
- git-svn dcommit and rebase was confused by patches that were
merged from another branch that is managed by git-svn.
----------------------------------------------------------------
Changes since v1.5.1 are as follows:
Arjen Laarhoven (4):
usermanual.txt: some capitalization nits
t3200-branch.sh: small language nit
t5300-pack-object.sh: portability issue using /usr/bin/stat
Makefile: iconv() on Darwin has the old interface
Brian Gernhardt (3):
Fix t4200-rerere for white-space from "wc -l"
Document --left-right option to rev-list.
Distinguish branches by more than case in tests.
Dana How (1):
Fix lseek(2) calls with args 2 and 3 swapped
Eric Wong (3):
git-svn: bail out on incorrect command-line options
git-svn: dcommit/rebase confused by patches with git-svn-id: lines
git-svn: fix log command to avoid infinite loop on long commit messages
Frank Lichtenheld (7):
cvsimport: sync usage lines with existing options
cvsimport: Improve documentation of CVSROOT and CVS module determination
cvsimport: Improve usage error reporting
cvsimport: Reorder options in documentation for better understanding
cvsimport: Improve formating consistency
cvsserver: small corrections to asciidoc documentation
cvsserver: Fix handling of diappeared files on update
Geert Bosch (1):
Fix renaming branch without config file
Gerrit Pape (1):
rename contrib/hooks/post-receieve-email to contrib/hooks/post-receive-email.
Jakub Narebski (1):
gitweb: Fix bug in "blobdiff" view for split (e.g. file to symlink) patches
Jim Meyering (1):
(encode_85, decode_85): Mark source buffer pointer as "const".
Julian Phillips (1):
Documentation: show-ref: document --exclude-existing
Junio C Hamano (7):
rerere: make sorting really stable.
Fix dependency of common-cmds.h
Documentation: tighten dependency for git.{html,txt}
Prepare for 1.5.1.1
Add Documentation/cmd-list.made to .gitignore
fsck: do not complain on detached HEAD.
GIT 1.5.1.1
Lars Hjemli (2):
rename_ref(): only print a warning when config-file update fails
Make builtin-branch.c handle the git config file
René Scharfe (1):
Revert "builtin-archive: use RUN_SETUP"
Shawn O. Pearce (1):
Honor -p<n> when applying git diffs
Tomash Brechko (1):
cvsexportcommit -p : fix the usage of git-apply -C.
Ville Skyttä (1):
DESTDIR support for git/contrib/emacs
YOSHIFUJI Hideaki (1):
Avoid composing too long "References" header.
next reply other threads:[~2007-04-12 2:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 2:09 Junio C Hamano [this message]
2007-04-22 6:16 ` [ANNOUNCE] GIT 1.5.1.2 Junio C Hamano
2007-04-22 17:22 ` Linus Torvalds
2007-04-22 17:58 ` Junio C Hamano
2007-04-22 18:06 ` Today's 'master' leaves .idx/.pack in 0400 Junio C Hamano
2007-04-22 18:25 ` Nicolas Pitre
2007-04-22 18:27 ` Junio C Hamano
2007-04-22 18:34 ` Nicolas Pitre
2007-04-22 18:47 ` Nicolas Pitre
2007-04-22 18:52 ` Junio C Hamano
2007-04-22 18:54 ` Linus Torvalds
2007-04-22 19:03 ` Junio C Hamano
2007-04-22 19:20 ` Junio C Hamano
2007-04-22 19:29 ` Linus Torvalds
2007-04-22 18:47 ` [ANNOUNCE] GIT 1.5.1.2 Junio C Hamano
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=7vhcrml4wx.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
all inboxes | Powered by JetHome®