{"thread":{"id":"43640","subject":"Re: What's cooking in git.git (topics)","startedAt":"2006-12-20T21:21:44Z","lastAt":"2006-12-20T23:51:46Z","messageCount":2,"participants":["Eric Wong","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"298404","messageId":"7vejqu8dqv.fsf@assigned-by-dhcp.cox.net","threadId":"43640","inReplyTo":null,"subject":"What's cooking in git.git (topics)","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-12-20T21:21:44Z","receivedAt":"2006-12-20T21:21:44Z","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/rerere (Wed Dec 20 17:39:41 2006 +0100) 3 commits\n - Make git-rerere a builtin\n - Add a test for git-rerere\n - move read_mmfile() into xdiff-interface\n\nRewrite of rerere in C by Johannes; this is supposed to contain\nno feature change, and I should be able to merge it anytime when\nit is shown to be correct.  We'll see.\n\n* jc/skip-count (Tue Dec 19 18:25:32 2006 -0800) 1 commit\n + revision: --skip=<n>\n\nThis could help gitweb, but otherwise no strong reason to merge\nto 'master' yet.\n\n* jc/leftright (Tue Dec 19 02:28:16 2006 -0800) 4 commits\n + Revert \"Make left-right automatic.\"\n + Make left-right automatic.\n + Teach all of log family --left-right output.\n + rev-list --left-right\n\nSince I reverted the 'automatic' bits, this is ready to be\nmerged to 'master'.  Perhaps in v1.5.0.\n\n* jc/fsck-reflog (Tue Dec 19 00:23:12 2006 -0800) 6 commits\n - git reflog expire\n - Move in_merge_bases() to commit.c\n - reflog: fix warning message.\n - Teach git-repack to preserve objects referred to by reflog\n   entries.\n - Protect commits recorded in reflog from pruning.\n - add for_each_reflog_ent() iterator\n\nBecause reflogs are enabled by default in end user repositories\nnow, this series will be needed sooner or later.  The earlier\nones prevent commits lost by reset/rebase from getting pruned\nwhile reflogs point at them, while the latter ones allow reflogs\nto be pruned.  Earlier parts cannot be merged without the expiry\nmechanism in the later ones, because doing so would mean crufts\nwill accumulate not just in reflogs but in object database,\nwithout an easy way to prune them.\n\n* jc/clone (Tue Dec 19 01:39:07 2006 +0100) 10 commits\n + Move \"no merge candidate\" warning into git-pull\n + Use preprocessor constants for environment variable names.\n + Do not create $GIT_DIR/remotes/ directory anymore.\n + Introduce GIT_TEMPLATE_DIR\n + Revert \"fix testsuite: make sure they use templates freshly built\n   from the source\"\n + fix testsuite: make sure they use templates freshly built from the\n   source\n + git-clone: lose the traditional 'no-separate-remote' layout\n + git-clone: lose the artificial \"first\" fetch refspec\n + git-pull: refuse default merge without branch.*.merge\n + git-clone: use wildcard specification for tracking branches\n\nThis is to conclude the move of the default repository layout\ncreated by git-clone to separate-remote layout.  I think this is\nready and the next push would include this in the 'master'.\n\n* jc/branch-remove-remote (Tue Dec 19 09:42:16 2006 +1100) 2 commits\n + git-branch -d: do not stop at the first failure.\n + Teach git-branch to delete tracking branches with -r -d\n\nWill merge.\n\n* jc/blame (Mon Dec 18 14:04:38 2006 -0800) 1 commit\n + blame: -b (blame.blankboundary) and --root (blame.showroot)\n\nWill merge.\n\n* jn/web (Sat Dec 16 17:12:55 2006 +0100) 1 commit\n - gitweb: Add some mod_perl specific support\n\nOn hold, Jakub's call.\n\n* ew/svn-pm (Fri Dec 15 23:58:08 2006 -0800) 3 commits\n + git-svn: rename 'commit' command to 'set-tree'\n + git-svn: remove support for the svn command-line client\n + git-svn: convert to using Git.pm\n\nI've heard a few comments that renaming 'commit' to 'set-tree'\nare received favorably by users, so this might be ready to be\nmerged.  Eric's call, but I am not in the rush.\n\n* jc/git-add--interactive (Wed Dec 20 13:06:46 2006 -0800) 3 commits\n . git-add: error out when given no arguments.\n + git-add --interactive: hunk splitting\n + git-add --interactive\n\nThis is a bit too young and I am not sure how useful it is in\npractice.  I might cherry-pick its tip to 'master' first without\nadding the --interactive bits.\n\n* jc/explain (Mon Dec 4 19:35:04 2006 -0800) 1 commit\n - git-explain\n\nProbably not in v1.5.0.\n\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\nNot in v1.5.0.\n\n* js/shallow (Fri Nov 24 16:00:13 2006 +0100) 15 commits\n + fetch-pack: Do not fetch tags for shallow clones.\n + get_shallow_commits: Avoid memory leak if a commit has been\n   reached already.\n + git-fetch: Reset shallow_depth before auto-following tags.\n + upload-pack: Check for NOT_SHALLOW flag before sending a shallow\n   to the client.\n + fetch-pack: Properly remove the shallow file when it becomes\n   empty.\n + shallow clone: unparse and reparse an unshallowed commit\n + Why didn't we mark want_obj as ~UNINTERESTING in the old code?\n + Why does it mean we do not have to register shallow if we have\n   one?\n + We should make sure that the protocol is still extensible.\n + add tests for shallow stuff\n + Shallow clone: do not ignore shallowness when following tags\n + allow deepening of a shallow repository\n + allow cloning a repository \"shallowly\"\n + support fetching into a shallow repository\n + upload-pack: no longer call rev-list\n\nPost v1.5.0.\n\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 (Mon Sep 25 23:03:34 2006 -0700) 1 commit\n - para-walk: walk n trees, index and working tree in parallel\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\nThe above four are on hold.\n"},{"id":"296188","messageId":"20061220235146.GA13647@localdomain","threadId":"43640","inReplyTo":"7vejqu8dqv.fsf@assigned-by-dhcp.cox.net","subject":"Re: What's cooking in git.git (topics)","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2006-12-20T23:51:46Z","receivedAt":"2006-12-20T23:51:46Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Junio C Hamano <junkio@cox.net> wrote:\n> * ew/svn-pm (Fri Dec 15 23:58:08 2006 -0800) 3 commits\n>  + git-svn: rename 'commit' command to 'set-tree'\n>  + git-svn: remove support for the svn command-line client\n>  + git-svn: convert to using Git.pm\n> \n> I've heard a few comments that renaming 'commit' to 'set-tree'\n> are received favorably by users, so this might be ready to be\n> merged.  Eric's call, but I am not in the rush.\n\nYes, please merge these for 1.5.0.  I have more on the way that depend\non these patches.  The coming changes to git-svn should make life easier\nfor Sam's svm/svk patches, too.\n\n-- \n"}]}