From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: What's in git/spearce.git (Oct 2008, #01; Mon, 06)
Date: Mon, 6 Oct 2008 09:59:08 -0700 [thread overview]
Message-ID: <20081006165908.GF8203@spearce.org> (raw)
What's in git/spearce.git (Oct 2008, #01; Mon, 06)
maint e261cf9 (Update release notes for 1.6.0.3)
master 276328f (Merge branch 'maint')
------------------------------------------------------------------------
Junio should be returning from vacation this week. I will keep
updating my git/spearce.git tree until he gets back and asks for
my current topic heads.
Once Junio gets back I think we need to focus on getting 1.6.0.3
out the door. We have 77 commits queued up since 1.6.0.2 and it
has been almost 4 weeks since our last maint release.
So please, test, test, test maint.
--------
* The 'maint' branch has these fixes since the last announcement.
Alexander Gavrilov (1):
builtin-blame: Fix blame -C -C with submodules.
David Soria Parra (1):
Solaris: Use OLD_ICONV to avoid compile warnings
Dmitry Potapov (2):
make prefix_path() never return NULL
do not segfault if make_cache_entry failed
Giuseppe Bilotta (1):
gitweb: remove PATH_INFO from $my_url and $my_uri
Jakub Narebski (2):
gitweb: Fix two 'uninitialized value' warnings in git_tree()
gitweb: Add path_info tests to t/t9500-gitweb-standalone-no-errors.sh
Linus Torvalds (1):
fix bogus "diff --git" header from "diff --no-index"
Luc Heinrich (1):
git-svn: call 'fatal' correctly in set-tree
Michael Prokop (1):
Replace svn.foo.org with svn.example.com in git-svn docs (RFC 2606)
Nanako Shiraishi (2):
docs: describe pre-rebase hook
Teach rebase -i to honor pre-rebase hook
SZEDER Gábor (3):
t0024: add executable permission
Documentation: remove '\' in front of short options
bash: remove fetch, push, pull dashed form leftovers
Shawn O. Pearce (1):
Update release notes for 1.6.0.3
Tuncer Ayaz (1):
Fix fetch/clone --quiet when stdout is connected
martin f. krafft (1):
Improve git-log documentation wrt file filters
* The 'master' branch has these since the last announcement
in addition to the above.
Brandon Casey (1):
diff.c: remove duplicate bibtex pattern introduced by merge 92bb9785
David Aguilar (1):
tests: add a testcase for "git submodule sync"
David Bryson (1):
Use "git_config_string" to simplify "builtin-gc.c" code where
"prune_expire" is set
Dmitry Potapov (1):
do not segfault if make_cache_entry failed
Jeff King (1):
tests: grep portability fixes
Jonathan del Strother (1):
Add OS X support to the pre-auto-gc example hook
Nanako Shiraishi (5):
dir.c: make dir_add_name() and dir_add_ignored() static
run-command.c: remove run_command_v_opt_cd()
config.c: make git_parse_long() static
commit.c: make read_graft_file() static
archive.c: make archiver static
Nicolas Pitre (1):
fix openssl headers conflicting with custom SHA1 implementations
Petr Baudis (3):
gitweb: Quote non-displayable characters in hex, not octal
config.c: Tolerate UTF8 BOM at the beginning of config file
gitweb: Identify all summary metadata table rows
Ralf Wildenhues (1):
Correct typos in RelNotes-1.6.1
SZEDER Gábor (1):
remove vim syntax highlighting in favor of upstream
--
Shawn.
reply other threads:[~2008-10-06 17:00 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=20081006165908.GF8203@spearce.org \
--to=spearce@spearce.org \
--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.
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).