From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: GIT 0.99.8
Date: Sun, 02 Oct 2005 17:12:13 -0700 [thread overview]
Message-ID: <7vfyrjxxuq.fsf@assigned-by-dhcp.cox.net> (raw)
Here is 0.99.8. GIT has been doing everything I personally
wanted it to do since mid 0.99.7, and now it has almost
everything I want it to contain, except for a couple of minor
points. I feel that we are ready to finish the last mile for
1.0. Many thanks to everybody who contributed the comments,
eyeballs, and code.
Done in 0.99.8
==============
New Features, Commands, and Enhancements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* 'git pull' now uses 'git-merge' instead of 'git-resolve', so you can
specify alternative merge strategy to use on its command line.
* 'git pull -s recursive' has been taught about renaming merges,
which may deal with HPA's klibc vs klibc-kbuild situation better.
* Symbolic refs -- instead of using symlinks to express .git/HEAD,
you can have a regular file that stores a single line
'ref: refs/heads/master' in it.
git-update-ref is the preferred way to write into .git/HEAD,
not "echo >.git/HEAD". git-symbolic-ref is the preferred way
to check which underlying ref a symbolic ref .git/HEAD refers
to, not "readlink .git/HEAD".
* A couple of new diff options (-l<num> and --name-status).
* Commit walker over http acquired more SSL options.
* 'git clone' checks out the working tree by default.
Fixes
~~~~~
* Removed unused commands (diff-helper, rev-tree, and export).
* Platforms with only Python 2.3 installed can use recursive merge
strategy.
* Octopus documented.
* Merge is more careful noticing potentially ambiguous situation.
* Git pull does not blindly do Octopus when Pull: lines in remotes
file specifies more than one remote branches.
* Commit walker got safer to use after interrupted downloads.
* Commit walker over http can resume partial downloads.
* More portability fixes for BSD and Solaris.
reply other threads:[~2005-10-03 0:12 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vfyrjxxuq.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).