git/list[1] front-page[2] threads[3] people[4] search[5] about
 

What's in git.git

From
Junio C Hamano <junkio@cox.net>
Date
Mar 15, 2006, 22:13 UTC
Message-ID
<7vk6avgxva.fsf@assigned-by-dhcp.cox.net>
* The 'master' branch has these since the last announcement.
 - git-svn updates (Eric Wong)
 - git-blame knows about renames (Fredrik Kuivinen)
 - imap-send (Mike McCormack with fixes from Johannes Schindelin
   and Marco Roeland)
 - cvsimport only updates tracking branch (Matthias Urlichs)
 - repo-config fix (Jonas Fonseca)
 - fmt-merge-msg cleanup (Linus Torvalds)
 - format-patch attachments enhancements (Mike McCormack)
 - delitifier cleanup and performance fix (Nicolas Pitre)
 - remove end-of-line period from git-pull message (Olaf Hering)
 - http-push and fetch updates (Nick Hengeveld)
 - rev-list and revision walker performance fix (Matthias Urlichs)
 - annotate RPM packaging workaround (sean)
 - assorted doc fixes (Francis Daly, Fredrik Kuivinen)
 - assorted test fixes (Mark Wooding, me)
 - improve git wrapper --help output (Fredrik Kuivinen)
 - checkout-index --temp (Shawn Pearce)
 - no more --standalone to fsck-objects
 - rev-list path limiter fix at boundary
 - git-diff: -p disables rename detection

As you can see from the above, the core part does not have drastic changes these days anymore. Just some boring fixes with a handful new and interesting developments.

In the "next" branch is the "insanely fast rename detection". I've done some minor fixups to its hash function to be usable on both 32-bit and 64-bit machines but otherwise it is what was posted by Linus to the list. It completes the rename detection between v2.6.12 and v2.6.14 kernel source under 5 seconds on my Duron 750 with slow disks, where the current "master" branch version takes about 60 seconds.

Also I've been keeping ls-{tree,files} --abbrev patches and refs/remotes patch from Eric Wong in 'next' and 'pu'. I haven't seen anybody jumps up and down to have them merged to "master", nor have been asked to push them out sooner so that a widely used Porcelain or two can take advantage of them, and that's the only reason why they are not in "master". In other words, while I do not have much against them, it would be nicer to have a convincing argument why they are must-have's or even better-have's before they graduate.

Next: Randal L. Schwartz
Message 1 of 3 in “What's in git.git”
  1. Junio C HamanoMar 15, 2006
  2. fix imap-send for OSXRandal L. Schwartz, Mar 15, 2006
  3. Junio C HamanoMar 15, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.