|| ||Junio C Hamano <email@example.com>|
|| ||firstname.lastname@example.org, email@example.com|
|| ||[ANNOUNCE] GIT 0.99.9l aka 1.0rc4|
|| ||Sun, 04 Dec 2005 01:21:13 -0800|
GIT 0.99.9l aka 1.0rc4 is found at a new location.
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.
- 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,
- 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
- 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.
*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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/