From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's in git.git (Sep 2008, #02; Wed, 10)
Date: Wed, 10 Sep 2008 20:49:40 -0700 [thread overview]
Message-ID: <7viqt3tk8b.fsf@gitster.siamese.dyndns.org> (raw)
There are still a few topics that are meant for 'maint' cooking in higher
stages; we will have 1.6.0.2 after they are merged down.
On the 'master' front, it looks like 1.6.1 will not have anything
particularly big like 1.6.0 did. Other than many s/git-foo/git foo/
updates in tests (finished -- the documentation needs to go through the
same process), there are many small bells and whistles enhancements, but
nothing earth shattering. I am expecting that we will go into 1.6.1-rc0
freeze in two weeks.
* The 'maint' branch has these fixes since the last announcement.
Arjen Laarhoven (1):
Use compatibility regex library for OSX/Darwin
Junio C Hamano (4):
checkout: do not check out unmerged higher stages randomly
diff: Help "less" hide ^M from the output
log --author/--committer: really match only with name part
Update draft release notes for 1.6.0.2
Marcus Griep (2):
Git.pm: Use File::Temp->tempfile instead of ->new
git-svn: Fixes my() parameter list syntax error in pre-5.8 Perl
Miklos Vajna (1):
t7501: always use test_cmp instead of diff
Nicolas Pitre (5):
pack-objects: improve returned information from write_one()
improve reliability of fixup_pack_header_footer()
pack-objects: use fixup_pack_header_footer()'s validation mode
index-pack: use fixup_pack_header_footer()'s validation mode
fixup_pack_header_footer(): use nicely aligned buffer sizes
* The 'master' branch has these since the last announcement
in addition to the above.
Alex Riesen (1):
Add help.autocorrect to enable/disable autocorrecting
Andreas Ericsson (1):
Teach "git diff -p" to locate PHP class methods
Arjen Laarhoven (1):
t6023-merge-file: Work around non-portable sed usage
Christian Couder (1):
refs: improve comments about "reading" argument of "resolve_ref"
Dotan Barak (1):
Use xmalloc() and friends to catch allocation failures
Eric Wong (1):
git-svn: fix handling of even funkier branch names
Giovanni Funchal (1):
configure: auto detect dynamic library path switches
Heikki Orsila (1):
Start conforming code to "git subcmd" style part 2
Johannes Schindelin (1):
git wrapper: DWIM mistyped commands
Johannes Sixt (1):
Windows: git-shell can be compiled again
Junio C Hamano (2):
Makefile: Allow CC_LD_DYNPATH to be overriden
Fix git-diff-tree --stdin
Michael J Gruber (2):
allow installation of man and html doc from the man and html branches
separate build targets for man and html documentation
Mikael Magnusson (1):
Correct output of git-count-objects.
Nanako Shiraishi (8):
t/t91XX-svn: start removing use of "git-" from these tests
t/t91XX git-svn tests: run "git svn" not "git-svn"
t9200: use "git cvsexportcommit" without dash
t9300, t9301: use "git fast-import/fast-export" without dash
t9700: use "git config" without dash
tests: use "git foo" without dash in strings
t9101: use "git hash-object" without dash
Install git-cvsserver in $(bindir)
next reply other threads:[~2008-09-11 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 3:49 Junio C Hamano [this message]
2008-09-11 9:09 ` What's in git.git (Sep 2008, #02; Wed, 10) Michael J Gruber
2008-09-11 22:02 ` 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=7viqt3tk8b.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.