{"thread":{"id":"6344","subject":"What's cooking in git.git (topics)","startedAt":"2007-01-12T02:43:48Z","lastAt":"2007-01-12T02:43:48Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"31535","messageId":"7vac0px8uz.fsf@assigned-by-dhcp.cox.net","threadId":"6344","inReplyTo":null,"subject":"What's cooking in git.git (topics)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-01-12T02:43:48Z","receivedAt":"2007-01-12T02:43:48Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking.  Commits prefixed\nwith '-' are only in 'pu' while commits prefixed with '+' are\nin 'next'.  The topics list the commits in reverse chronological\norder.\n\n* js/reflog (Thu Jan 11 11:47:48 2007 +0100) 1 commit\n - Teach the revision walker to walk by reflogs with --walk-reflogs\n\nIt appears to show list of commits with reflog messages, but I\nam not sure how useful it is until I get used to its output.\n\nOne question I keep asking reflog has been:\n\n\tWhen was commit X pushed out as part of 'master'?\n\nI have reflog on a tracking branch that I fetch from the public\ngit.git repository immediately after I push into it, so it is a\nmatter of walking the reflog for that branch and see which one\nis the earliest one that is a descendant of the commit in\nquestion.  It does not tell me about the mirroring lags, but at\nleast let me keep track of when I pushed something out.\n\n\n* jc/merge-base (Tue Jan 9 02:23:42 2007 -0800) 6 commits\n - Teach \"git-merge-base --check-ancestry\" about refs.\n - git-merge-base: --check-ancestry option\n + in_merge_bases(): optimization\n + merge_base(): move traversal into a separate function.\n + Allow in_merge_bases() to take more than one reference commits.\n + Make merge-base a built-in.\n* sp/merge (Thu Dec 28 02:35:17 2006 -0500) 2 commits\n - Avoid git-fetch in `git-pull .` when possible.\n + Improve merge performance by avoiding in-index merges.\n* jc/diff (Mon Dec 25 01:08:50 2006 -0800) 2 commits\n - test-para: combined diff between HEAD, index and working tree.\n - para-walk: walk n trees, index and working tree in parallel\n* jc/explain (Mon Dec 4 19:35:04 2006 -0800) 1 commit\n - git-explain\n* jc/3way (Wed Nov 29 18:53:13 2006 -0800) 1 commit\n + git-merge: preserve and merge local changes when doing fast\n   forward\n* jc/web (Wed Nov 8 14:54:09 2006 -0800) 1 commit\n - gitweb: steal loadavg throttle from kernel.org\n* jc/pickaxe (Sun Nov 5 11:52:43 2006 -0800) 1 commit\n - blame: --show-stats for easier optimization work.\n* jc/diff-apply-patch (Fri Sep 22 16:17:58 2006 -0700) 1 commit\n + git-diff/git-apply: make diff output a bit friendlier to GNU patch\n   (part 2)\n\nThese are on hold.\n"}]}