git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4
Date: Sun, 04 Dec 2005 01:21:13 -0800	[thread overview]
Message-ID: <7vy831p69i.fsf@assigned-by-dhcp.cox.net> (raw)

GIT 0.99.9l aka 1.0rc4 is found at a new location.

RPM
	http://kernel.org:/pub/software/git/RPMS/

Debian [*1*]
	http://kernel.org:/pub/software/git/debian/

This is mostly fixes, with some improvements.  As I said on the
git list earlier, no more major feature/semantics changes after
this is expected until 1.0.

Highlights are:

 - After a conflicting merge, the index file is left unmerged.
   As before, after such conflicting merge, "git diff" can be
   used to view the differences between the half-merged file and
   "our" branch version by default, but now you can say "git
   diff --base" and "git diff --theirs" to view the differences
   since the merge-base version and the other branch's version,
   respectively.

 - git-daemon and other git native protocols allow user-relative
   paths (e.g. git://host/~user/repo).  git-daemon's path
   whitelist check used to be done with the realpath (i.e. what
   getcwd() returns) in 0.99.9k and later "master" branch
   versions, but it was changed back to check against what the
   requester asked.

 - The commands have been future-proofed so that they refuse to
   operate on repositories from future unknown versions, to
   avoid corrupting them by mistake.

 - Bisect can take pathspec to cut down the number of revisions
   that need to be tested.

 - Many low-level commands have been updated to work better from
   subdirectories (much of the barebone porcelain wrappers that
   deal with the whole repository or the whole tree still need
   to be run from the top level, though).

 - Merge used to fail when it removed a file (fixed).

 - When only GIT_OBJECT_DIRECTORY was exported things broke
   since 0.99.9k (fixed).

 - Comes with updated gitk.

[Footnote]

*1* It appears Debian finally has an official maintainer, so I
am inclined to stop building and supplying the debs starting
from the next version --- one less thing to worry about for me.
I hope the Debian side splits the packages along the same line
as we do RPMs.

             reply	other threads:[~2005-12-04  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04  9:21 Junio C Hamano [this message]
2005-12-04 20:16 ` [ANNOUNCE] GIT 0.99.9l aka 1.0rc4 Horst von Brand
2005-12-04 20:49   ` H. Peter Anvin
2005-12-05 17:26 ` Gerrit Pape
2005-12-05 20:16   ` Junio C Hamano
2005-12-05 21:10     ` Jon Loeliger
2005-12-07 16:20     ` Gerrit Pape

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=7vy831p69i.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;
as well as URLs for NNTP newsgroup(s).