On Mon, 2008-06-30 at 02:08 -0700, Junio C Hamano wrote: > Here are the topics that have been cooking. Commits prefixed > with '-' are only in 'pu' while commits prefixed with '+' are > in 'next'. > > The topics list the commits in reverse chronological order. The topics > meant to be applied to the maintenance series have "maint-" in their > names. > > It already is beginning to become clear what 1.6.0 will look like. What's > already in 'next' all are well intentioned (I do not guarantee they are > already bug-free --- that is what cooking them in 'next' is for) and are > good set of feature enhancements. Bigger changes will be: > > * MinGW will be in. > > * With the default Makefile settings, most of the programs will be > installed outside your $PATH, except for "git", "gitk", "git-gui" and > some server side programs that need to be accessible for technical > reasons. Invoking a git subcommand as "git-xyzzy" from the command > line has been deprecated since early 2006 (and officially announced in > 1.5.4 release notes); use of them from your scripts after adding > output from "git --exec-path" to the $PATH will still be supported in > 1.6.0, but users are again strongly encouraged to adjust their > scripts to use "git xyzzy" form, as we will stop installing > "git-xyzzy" hardlinks for built-in commands in later releases. > > * git-merge will be rewritten in C. > > * default pack and idx versions will be updated as scheduled for some > time ago. A small detail I've suggested scheduling for 1.6 before is removing (or rather, stop creating) the empty .git/branches directory. How does that sound? cheers, Kristian -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
