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.
------------------------
To graduate immediately after 1.5.2, after 'maint' forks from
it.
* jb/statcolor (Sat May 5 16:48:54 2007 -0400) 1 commit
+ Add colour support in rebase and merge tree diff stats output.
* tt/gc (Wed May 9 15:48:39 2007 -0400) 1 commit
+ Add --aggressive option to 'git gc'
* np/pack (Wed May 9 14:42:42 2007 -0400) 3 commits
+ deprecate the new loose object header format
+ make "repack -f" imply "pack-objects --no-reuse-object"
+ allow for undeltified objects not to be reused
* sv/checkout (Wed May 9 12:33:20 2007 +0200) 1 commit
+ git-update-ref: add --no-deref option for overwriting/detaching
ref
* mst/connect (Wed May 16 20:09:41 2007 +0300) 1 commit
+ connect: display connection progress
* dh/pack (Wed May 9 13:56:50 2007 -0700) 3 commits
+ Custom compression levels for objects and packs
+ make "repack -f" imply "pack-objects --no-reuse-object"
+ allow for undeltified objects not to be reused
------------------------
To be re-reviewed and then merged to 'next' after 1.5.2.
* db/remote (Tue May 15 22:50:19 2007 -0400) 5 commits
- Update local tracking refs when pushing
- Add handlers for fetch-side configuration of remotes.
- Move refspec parser from connect.c and cache.h to remote.{c,h}
- Move remote parsing into a library file out of builtin-push.
* dh/repack (Sun May 13 12:47:09 2007 -0700) 9 commits
- git-repack --max-pack-size: add option parsing to enable feature
- git-repack --max-pack-size: split packs as asked by
write_{object,one}()
- git-repack --max-pack-size: write_{object,one}() respect pack
limit
- git-repack --max-pack-size: new file statics and code
restructuring
- Alter sha1close() 3rd argument to request flush only
------------------------
I've queued this series only because I trust Pasky, not because I
looked at the code deeply. I am not sure about this one's use
of JavaScript is acceptable (I haven't looked at the code and do
not even know if that is optional X-< Yes, I know, My Bad).
* pb/web (Sat May 19 02:13:39 2007 +0200) 6 commits
- gitweb: Clearly distinguish regexp / exact match searches
- gitweb: Lift any characters restriction on searched strings
- git-rev-list: Add regexp tuning options
- gitweb: Remove git_blame (superseded by git_blame2)
- gitweb: Extra columns in blame
- gitweb: Incremental blame
------------------------
On hold.
* jc/blame (Fri Apr 20 16:25:50 2007 -0700) 4 commits
- blame: show log as it goes
- git-blame: optimize get_origin() from linear search to hash-
lookup.
- git-blame: pass "struct scoreboard *" pointers around.
- blame: lift structure definitions up
* jc/diff (Mon Dec 25 01:08:50 2006 -0800) 2 commits
- test-para: combined diff between HEAD, index and working tree.
- para-walk: walk n trees, index and working tree in parallel
-
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
