From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.0.7
Date: Fri, 06 Jan 2006 23:01:34 -0800 [thread overview]
Message-ID: <7vhd8go71t.fsf@assigned-by-dhcp.cox.net> (raw)
GIT 1.0.7 is available at http://www.kernel.org/pub/software/scm/git/
Just bunch of cleanups, documentation formatting and spelling
fixes, among them notable are:
- git-format-patch and git-commit now handles author names with
' (ASCII 0x27, single quote) character in them properly.
- approxidate parser does not get confused when we say "10 days
ago" immediately after new year.
The master branch has accumulated enough enhancements, and I
plan to do GIT 1.1.0 (and start 1.1.X maintenance series) over
the weekend. What will be there are listed here, but those who
have been running the "master" branch must be familiar with most
of them.
Johannes Schindelin:
git-clone: Support changing the origin branch with -o
Introduce core.sharedrepository
git-init-db: initialize shared repositories with --shared
John Ellson:
Make GIT-VERSION-GEN tolerate missing git describe command
Junio C Hamano:
Versioning scheme changes.
merge-recursive: conflicting rename case.
whatchanged: customize diff-tree output
rev-parse: --show-cdup
check_packed_git_idx(): check integrity of the idx file itself.
checkout: sometimes work from a subdirectory.
ls-tree: chomp leading directories when run from a subdirectory
git-clone: do not special case dumb http.
Tutorial: mention shared repository management.
git-describe: really prefer tags only.
git-describe: use find_unique_abbrev()
git-describe: --tags and --abbrev
git-describe: still prefer annotated tag under --all and --tags
git-describe: documentation.
Makefile: use git-describe to mark the git version.
send-pack/receive-pack: allow errors to be reported back to pusher.
Linus Torvalds:
Add a "git-describe" command
Lukas Sandstrom:
git-pack-redundant: speed and memory usage improvements
YOSHIFUJI Hideaki:
GIT: Support [address] in URLs
reply other threads:[~2006-01-07 7:01 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=7vhd8go71t.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®