From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: GIT 1.5.6-rc3
Date: Sat, 14 Jun 2008 22:16:58 -0700 [thread overview]
Message-ID: <7v63sbe0qd.fsf@gitster.siamese.dyndns.org> (raw)
I've pushed out 1.5.6-rc3 to kernel.org. Nothing majorly disrupting nor
scary here.
--
Ask Bjørn Hansen (2):
gitweb setup instruction: rewrite HEAD and root as well
send-email: Allow the envelope sender to be set via configuration
Avery Pennarun (2):
git-svn: don't append extra newlines at the end of commit messages.
git-svn: test that extra blank lines aren't inserted in commit messages.
Boyd Lynn Gerber (2):
progress.c: avoid use of dynamic-sized array
Port to 12 other Platforms.
Chris Ridd (1):
Improve sed portability
Christian Couder (1):
documentation: bisect: remove bits talking about a bisection branch
Flavio Poletti (1):
git-instaweb: improve auto-discovery of httpd and call conventions.
Fred Maranhão (1):
fix typo in tutorial
Geoffrey Irving (1):
doc: adding gitman.info and *.texi to .gitignore
Jakub Narebski (2):
gitweb: Make it work with $GIT containing spaces
Use 'trash directory' thoroughly in t/test-lib.sh
Jeff King (1):
document --pretty=tformat: option
Johannes Schindelin (1):
merge-recursive: respect core.autocrlf when writing out the result
Johannes Sixt (2):
make_nonrelative_path: Use is_absolute_path()
Remove exec bit from builtin-fast-export.c
Junio C Hamano (8):
http-push.c: remove duplicated code
"remote prune": be quiet when there is nothing to prune
Documentation/git-pull.txt: Use more standard [NOTE] markup
Documentation: exclude @pxref{[REMOTES]} from texinfo intermediate output
user-manual: describe how higher stages are set during a merge
t4126: fix test that happened to work due to timing
sha1_file.c: dead code removal
GIT 1.5.6-rc3
Lea Wiemann (4):
t1006-cat-file.sh: typo
cat-file --batch / --batch-check: do not exit if hashes are missing
Documentation/git-cat-file.txt: add missing line break
t/.gitattributes: only ignore whitespace errors in test files
Linus Torvalds (4):
Consolidate SHA1 object file close
Avoid cross-directory renames and linking on object creation
Make loose object file reading more careful
Simplify and rename find_sha1_file()
Marius Storm-Olsen (1):
Add testcase for merging in a CRLF repo
Mark Levedahl (1):
git-submodule - Fix errors regarding resolve_relative_url
Mikael Magnusson (1):
Typo in RelNotes.
Mike Hommey (1):
Don't allocate too much memory in quote_ref_url
Miklos Vajna (3):
Remove unused code in parse_commit_buffer()
git-rebase -i: mention the short command aliases in the todo list
git-read-tree: document -v option.
Olivier Marin (4):
remote show: fix the -n option
builtin-remote: split show_or_prune() in two separate functions
remote prune: print the list of pruned branches
remote show: list tracked remote branches with -n
Paul Mackerras (1):
gitk: Handle detached heads better
Philippe Bruhat (BooK) (1):
git-cvsimport: do not fail when CVSROOT is /
Pieter de Bie (1):
git-send-email: allow whitespace in addressee list
René Scharfe (1):
Ignore .gitattributes in bare repositories
SZEDER Gábor (2):
git add: add long equivalents of '-u' and '-f' options
completion: add more 'git add' options
Shawn O. Pearce (1):
fast-export: Correctly generate initial commits with no parents
Stephan Beyer (6):
git-commit.txt: Correct option alternatives
git-commit.txt: Add missing long/short options
Docs: Use "-l::\n--long\n" format in OPTIONS sections
Docs: add some long/short options
git-describe.txt: document --always
git-name-rev.txt: document --no-undefined and --always
reply other threads:[~2008-06-15 5:18 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v63sbe0qd.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).