From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: GIT 0.99.9f
Date: Tue, 08 Nov 2005 08:46:27 -0800 [thread overview]
Message-ID: <7vy83zhyu4.fsf@assigned-by-dhcp.cox.net> (raw)
This is more like a "current snapshot" rather than "contains
important fixes -- please update".
Much of the changes are documentation fixes, but there are two
new toys to play with.
- git-push is now aware of push over DAV (Nick)
- git-cvs suite has 'exportcommit' to play git commits back at
CVS (Martin).
---
Alex Riesen:
ls-files and read-tree need core.filemode
Fredrik Kuivinen:
merge-recursive: Only print relevant rename messages
Johannes Schindelin:
Small bugfixes for http-push.c
Jon Loeliger:
Refactored merge options into separate merge-options.txt.
Add bug isolation howto, scraped from Linus.
Add --tags documentation, scraped from JC mail.
Use consistent shell prompts and example style.
Junio C Hamano:
Documentation: talk about guts of merge in tutorial.
Recover dropped +x bit from git-pull.sh by accident.
Do not fail on hierarchical tagnames.
Documentation: asciidoc formatting fix for git-cvsexportcommit doc.
Fix documentation dependency generation.
Ignore more generated files.
Documentation: fix dependency generation.
Tutorial: do not use 'git resolve'.
Debian: packaging updates.
git-am: do not lose already edited final-commit when resuming.
GIT 0.99.9f
Kai Ruemmler:
Documentation update: use git branch -d foo where applicable
Martin Langhoff:
Introducing: git-cvsexportcommit
Nick Hengeveld:
Make http-push smarter about creating remote dirs
Add support for git-http-push to git-push script
next reply other threads:[~2005-11-08 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 16:46 Junio C Hamano [this message]
2005-11-09 7:02 ` [PATCH] fix cvsexportcommit syntax error Alexander Litvinov
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=7vy83zhyu4.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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.