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. > > > * jc/fsck-reflog (Fri Dec 22 23:42:30 2006 -0800) 9 commits > + reflog expire: do not punt on tags that point at non commits. > + reflog expire: prune commits that are not incomplete > + Don't crash during repack of a reflog with pruned commits. > + git reflog expire > + Move in_merge_bases() to commit.c > + reflog: fix warning message. > + Teach git-repack to preserve objects referred to by reflog > entries. > + Protect commits recorded in reflog from pruning. > + add for_each_reflog_ent() iterator > > I'd like to push this out before we go -rc1, since the reflogs > are now enabled by default, and otherwise would grow unbounded. I'd still like the preserving reflogged data during pruning and repacking to be optional (default to on). But failing that I'd like to have option to "reflog expire" to remove only specific (pattern match, prefix match?) entries, for example to remove all the "commit --amend" and StGIT work, but leaving rebases, resets, merges and other stuff. > * jn/web (Sat Dec 16 17:12:55 2006 +0100) 1 commit > - gitweb: Add some mod_perl specific support I'm about to send improved series of patches, few first ready to be applied, the rest for review. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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