* What's in git.git (with specific RFHs)
@ 2006-02-21 11:23 Junio C Hamano
0 siblings, 0 replies; only message in thread
From: Junio C Hamano @ 2006-02-21 11:23 UTC (permalink / raw)
To: git
* The 'master' branch has these since the last announcement.
- more portability bits from Johannes.
I'm holding off Makefile changes because it seems to trigger
"make -j" breakage. Testing, diagnosing and fixing the
version in the 'next' branch by more knowledgeable people is
very much appreciated.
- merge-tree by Linus.
- git-mktree: reverse of git-ls-tree.
I am hoping that this may help a new merge engine based on
merge-tree by Linus, but maybe not. It depends on how you
use merge-tree output.
- loosening "empty ident" errors.
Enough people seem to have been bitten by this since 1.2.0
was released.
- Fix fmt-merge-msg counting.
- cherry-pick/revert: rewording error-help message.
- git-svn updates from Erig Wong (contrib/).
* The 'next' branch, in addition, has these.
- "Assume unchanged git".
I have been using this in production for some time, without
usin CE_VALID, and am reasonably sure this does not break
anything for normal use. I am hoping to push this one to
'master' sometime this week. If people can find missing or
incomplete docs in this part, help is appreciated.
- Solaris 9+ portability bits from Paul Jakma.
Testing by people with Solaris 8 boxes to make sure this does
not regress and/or people with Solaris 9 or 10 boxes to see
if this help is appreciated. Quite likely to be "master"
material without further changes.
- Reusing data from existing packs, and "Thin pack" bandwidth
reduction for "git push" and "git fetch".
I am holding these off not because they are risky (I've been
using them in the production over the long weekend), but I'm
keeping them to entice people to try out the 'next' branch
;-). Quite likely to be "master" material without further
changes.
- Perl 5.6 backward compatibility.
Instead of open($fh, '-|', @list), use a bit older equivalent
form. Thanks for Johannes and Eric Wong. Quite likely to be
"master" material without further changes.
- git-annotate by Ryan and git-blame by Fredrik.
The one by Fredrik, being all in C, doing all git things
internally and forking only diff, seems much faster, but it
seems to have inherited bugs from my original blame script
implementation from long time ago. Ryan's one seems to be
computing sensible results.
* The 'pu' branch, in addition, has these.
- "Bash completion" in Ben Clifford (contrib/)
Without requests from the list, I am not particularly
interested in carrying this in my tree, but I wanted to try
out "an even cooler merge" myself, just like Linus did with
gitk merge.
- "Bound commit" lowlevel machinery for subprojects support.
Honestly, I am not very interested in this myself. If
somebody is interested in gitlink based subproject support,
the parts this touches would interfere with it -- in which
case I'd drop this.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-02-21 11:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-21 11:23 What's in git.git (with specific RFHs) Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox