delta/git.git, branch nd/find-pack-entry-recent-cache-invalidation

find_pack_entry(): do not keep packed_git pointer locally

2012-02-01T22:12:42+00:00

Commit f7c22cc (always start looking up objects in the last used pack
first - 2007-05-30) introduce a static packed_git* pointer as an
optimization.  The kept pointer however may become invalid if
free_pack_by_name() happens to free that particular pack.

Current code base does not access packs after calling
free_pack_by_name() so it should not be a problem. Anyway, move the
pointer out so that free_pack_by_name() can reset it to avoid running
into troubles in future.

Signed-off-by: Nguyễn Thái Ngọc Duy 
Acked-by: Nicolas Pitre 
Signed-off-by: Junio C Hamano

sha1_file.c: move the core logic of find_pack_entry() into fill_pack_entry()

2012-02-01T22:12:41+00:00

The new helper function implements the logic to find the offset for the
object in one pack and fill a pack_entry structure. The next patch will
restructure the loop and will call the helper from two places.

Signed-off-by: Nguyễn Thái Ngọc Duy 
Acked-by: Nicolas Pitre 
Signed-off-by: Junio C Hamano

Git 1.7.9

2012-01-27T19:31:02+00:00

Signed-off-by: Junio C Hamano

INSTALL: warn about recent Fedora breakage

2012-01-27T05:51:29+00:00

Recent releases of Redhat/Fedora are reported to ship Perl binary package
with some core modules stripped away (see http://lwn.net/Articles/477234/)
against the upstream Perl5 people's wishes. The Time::HiRes module used by
gitweb one of them.

Signed-off-by: Junio C Hamano

git-completion: workaround zsh COMPREPLY bug

2012-01-26T22:03:51+00:00

zsh adds a backslash (foo\ ) for each item in the COMPREPLY array if IFS
doesn't contain spaces. This issue has been reported[1], but there is no
solution yet.

This wasn't a problem due to another bug[2], which was fixed in zsh
version 4.3.12. After this change, 'git checkout ma' would resolve
to 'git checkout master\ '.

Aditionally, the introduction of __gitcomp_nl in commit a31e626
(completion: optimize refs completion) in git also made the problem
apparent, as Matthieu Moy reported.

The simplest and most generic solution is to hide all the changes we do
to IFS, so that "foo \nbar " is recognized by zsh as "foo bar". This
works on versions of git before and after the introduction of
__gitcomp_nl (a31e626), and versions of zsh before and after 4.3.12.

Once zsh is fixed, we should conditionally disable this workaround to
have the same benefits as bash users.

[1] http://www.zsh.org/mla/workers/2012/msg00053.html
[2] http://zsh.git.sourceforge.net/git/gitweb.cgi?p=zsh/zsh;a=commitdiff;h=2e25dfb8fd38dbef0a306282ffab1d343ce3ad8d

Signed-off-by: Felipe Contreras 
Signed-off-by: Junio C Hamano

docs: minor grammar fixes for v1.7.9 release notes

2012-01-26T19:09:08+00:00

Signed-off-by: Jeff King 
Signed-off-by: Junio C Hamano

Fix typo in 1.7.9 release notes

2012-01-23T18:11:13+00:00

Signed-off-by: Michael Haggerty 
Signed-off-by: Junio C Hamano

Git 1.7.9-rc2

2012-01-18T23:53:35+00:00

Signed-off-by: Junio C Hamano

Merge branch 'maint'

2012-01-18T23:52:08+00:00

* maint:
  Git 1.7.8.4
  Git 1.7.7.6
  diff-index: enable recursive pathspec matching in unpack_trees

Conflicts:
	GIT-VERSION-GEN

Git 1.7.8.4

2012-01-18T23:51:00+00:00

Signed-off-by: Junio C Hamano