{"thread":{"id":"43610","subject":"Re: What's in git.git","startedAt":"2006-11-25T10:12:38Z","lastAt":"2006-11-29T10:21:21Z","messageCount":3,"participants":["Carl Worth","Junio C Hamano","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"297112","messageId":"7vzmaf3kdl.fsf@assigned-by-dhcp.cox.net","threadId":"43610","inReplyTo":null,"subject":"What's in git.git","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-11-25T10:12:38Z","receivedAt":"2006-11-25T10:12:38Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Executive Summary\n=================\n\nThe 'maint' branch still has a handful more post v1.4.4.1\nfixes.\n\nAside from the usual gitweb and git-svn updates, the 'master'\nbranch has one notable change that everybody should hopefully\nwelcome.  separate-remote layout is now the default for newly\ncloned repositories.  We would be needing documentation updates\nand probably some more minor fixes for fallout from this, but I\ndo not expect anything majorly broken.\n\nCooking in 'next' are handful topics:\n\n * \"git shortlog bottom..top\" can be used instead of a pipeline\n   \"git log bottom..top | git shortlog\".\n\n * \"git merge -m message <commit>\" is another natural way to\n   perform a local merge, in addition to the traditional\n   \"git pull . <localbranch>\".  The former is more powerful in\n   that it can take arbitrary <committish>, not just a ref.\n\n * The new \"--depth $n\" parameter to git clone/fetch tries to\n   limit the commit ancestry depth to $n.  This still has known\n   issues (for example, shallowly cloning the git.git repository\n   and then deepening the result with large --depth parameter\n   later does not seem to make the resulting repository fully\n   connected, and fsck-objects reports corruption), so please\n   handle it with care.\n\n * \"git show-ref\", especially the \"-d\" variant, is much more\n   efficient when used in a repository with pack-pruned refs.\n\n * \"git fetch\" can fetch from a repository with pack-pruned refs\n   over dumb protocol transports.\n\n * \"git push $URL '':$ref\" can be used to delete an existing ref\n   from the remote side.\n\n * A glob pattern \"Pull: refs/heads/*:refs/remotes/origin/*\" is\n   allowed in the remotes file.  The fetch can be forced by\n   prefixing the specification with a '+'.\n\nCurrently 'pu' does not have much to speak of.\n\nThis update has rather large impact so the kernel list is CC'ed.\n\n----------------------------------------------------------------\n\n* The 'maint' branch has these fixes since the last announcement.\n\n   Andy Parkins (1):\n      Increase length of function name buffer\n\n   Eric Wong (3):\n      git-svn: error out from dcommit on a parent-less commit\n      git-svn: correctly handle revision 0 in SVN repositories\n      git-svn: preserve uncommitted changes after dcommit\n\n   René Scharfe (1):\n      archive-zip: don't use sizeof(struct ...)\n\n\n* The 'master' branch has these since the last announcement.\n\n   Andy Parkins (3):\n      Improve git-prune -n output\n      Add support to git-branch to show local and remote branches\n      Increase length of function name buffer\n\n   Eric Wong (6):\n      git-svn: error out from dcommit on a parent-less commit\n      git-svn: correctly handle revision 0 in SVN repositories\n      git-svn: preserve uncommitted changes after dcommit\n      git-svn: handle authentication without relying on cached tokens on disk\n      git-svn: correctly access repos when only given partial read permissions\n      git-svn: exit with status 1 for test failures\n\n   Iñaki Arenaza (1):\n      git-cvsimport: add support for CVS pserver method HTTP/1.x proxying\n\n   Jakub Narebski (8):\n      gitweb: Protect against possible warning in git_commitdiff\n      gitweb: Buffer diff header to deal with split patches + git_patchset_body refactoring\n      gitweb: Default to $hash_base or HEAD for $hash in \"commit\" and \"commitdiff\"\n      gitweb: New improved formatting of chunk header in diff\n      gitweb: Add an option to href() to return full URL\n      gitweb: Refactor feed generation, make output prettier, add Atom feed\n      gitweb: Finish restoring \"blob\" links in git_difftree_body\n      gitweb: Replace SPC with &nbsp; also in tag comment\n\n   Junio C Hamano (9):\n      upload-pack: stop the other side when they have more roots than we do.\n      apply --numstat: mark binary diffstat with - -, not 0 0\n      pack-objects: tweak \"do not even attempt delta\" heuristics\n      refs outside refs/{heads,tags} match less strongly.\n      Typefix builtin-prune.c::prune_object()\n      gitweb: (style) use chomp without parentheses consistently.\n      git-clone: stop dumb protocol from copying refs outside heads/ and tags/.\n      git-branch -D: make it work even when on a yet-to-be-born branch\n      git-fetch: exit with non-zero status when fast-forward check fails\n\n   Lars Hjemli (1):\n      Add -v and --abbrev options to git-branch\n\n   Peter Baumann (1):\n      config option log.showroot to show the diff of root commits\n\n   Petr Baudis (1):\n      Make git-clone --use-separate-remote the default\n\n   René Scharfe (1):\n      archive-zip: don't use sizeof(struct ...)\n\n\n* The 'next' branch, in addition, has these.\n\n   Alexandre Julliard (6):\n      Shallow clone: do not ignore shallowness when following tags\n      fetch-pack: Properly remove the shallow file when it becomes empty.\n      upload-pack: Check for NOT_SHALLOW flag before sending a shallow to the client.\n      git-fetch: Reset shallow_depth before auto-following tags.\n      get_shallow_commits: Avoid memory leak if a commit has been reached already.\n      fetch-pack: Do not fetch tags for shallow clones.\n\n   Jakub Narebski (1):\n      gitweb: Do not use esc_html in esc_path\n\n   Johannes Schindelin (10):\n      Build in shortlog\n      shortlog: do not crash on parsing \"[PATCH\"\n      shortlog: read mailmap from ./.mailmap again\n      shortlog: handle email addresses case-insensitively\n      shortlog: fix \"-n\"\n      upload-pack: no longer call rev-list\n      support fetching into a shallow repository\n      allow cloning a repository \"shallowly\"\n      allow deepening of a shallow repository\n      add tests for shallow stuff\n\n   Junio C Hamano (19):\n      Store peeled refs in packed-refs file.\n      remove merge-recursive-old\n      git-merge: make it usable as the first class UI\n      merge: allow merging into a yet-to-be-born branch.\n      git-diff/git-apply: make diff output a bit friendlier to GNU patch (part 2)\n      Store peeled refs in packed-refs (take 2).\n      git-fetch: reuse ls-remote result.\n      git-fetch: fix dumb protocol transport to fetch from pack-pruned ref\n      git-fetch: allow glob pattern in refspec\n      Allow git push to delete remote ref.\n      We should make sure that the protocol is still extensible.\n      Why does it mean we do not have to register shallow if we have one?\n      Why didn't we mark want_obj as ~UNINTERESTING in the old code?\n      shallow clone: unparse and reparse an unshallowed commit\n      git-shortlog: fix common repository prefix abbreviation.\n      git-shortlog: make common repository prefix configurable with .mailmap\n      git-commit: show --summary after successful commit.\n      git-fetch: allow forcing glob pattern in refspec\n      fetch-pack: do not barf when duplicate re patterns are given\n\n   Nicolas Pitre (1):\n      builtin git-shortlog is broken\n\n\n* The 'pu' branch, in addition, has these.\n\n   Junio C Hamano (4):\n      para-walk: walk n trees, index and working tree in parallel\n      rev-list --left-right\n      blame: --show-stats for easier optimization work.\n      gitweb: steal loadavg throttle from kernel.org\n\n"},{"id":"295953","messageId":"87zmabv0i7.wl%cworth@cworth.org","threadId":"43610","inReplyTo":"7vzmaf3kdl.fsf@assigned-by-dhcp.cox.net","subject":"Re: What's in git.git","fromName":"Carl Worth","fromEmail":"cworth@cworth.org","sentAt":"2006-11-28T19:23:28Z","receivedAt":"2006-11-28T19:23:28Z","isPatch":false,"sender":{"key":"cworth@cworth.org","avatar":"https://gravatar.com/avatar/3746dc28cde609bdbd7f939058356e7e2bbd16d21e32274df0725eb3d998bc5b?d=mp&s=160"},"body":"On Sat, 25 Nov 2006 02:12:38 -0800, Junio C Hamano wrote:\n>  * The new \"--depth $n\" parameter to git clone/fetch tries to\n>    limit the commit ancestry depth to $n.\n\nI'm very excited to see the shallow clone stuff coming online. Thanks\nto everybody that is working on that!\n\nHas though been given to make the depth selection consistent with\nother limiting options for rev-parse and rev-list? For example, I'd\nlike to be able to use --since to get a shallow clone, (so should\n--depth instead be --max-count?, and can we re-use some existing\nmachinery here?).\n\n>    Petr Baudis (1):\n>       Make git-clone --use-separate-remote the default\n...\n>    Junio C Hamano (19):\n>       git-merge: make it usable as the first class UI\n\nAlso very exciting. Please do keep up the user-interface improvements,\neverybody.\n\n-Carl\n"},{"id":"298364","messageId":"Pine.LNX.4.63.0611291118160.30004@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"43610","inReplyTo":"87zmabv0i7.wl%cworth@cworth.org","subject":"Re: What's in git.git","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-11-29T10:21:21Z","receivedAt":"2006-11-29T10:21:21Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 28 Nov 2006, Carl Worth wrote:\n\n> On Sat, 25 Nov 2006 02:12:38 -0800, Junio C Hamano wrote:\n> >  * The new \"--depth $n\" parameter to git clone/fetch tries to\n> >    limit the commit ancestry depth to $n.\n> [...]\n> Has though been given to make the depth selection consistent with\n> other limiting options for rev-parse and rev-list? For example, I'd\n> like to be able to use --since to get a shallow clone, (so should\n> --depth instead be --max-count?, and can we re-use some existing\n> machinery here?).\n\nI briefly considered that, but decided against it, for two reasons: 1) it \nputs the burden of calculation on the server, and 2) I was not at all sure \nif the whole shallow stuff would be useful to begin with (and therefore \navoided complicated stuff as much as possible).\n\n> >    Petr Baudis (1):\n> >       Make git-clone --use-separate-remote the default\n> ...\n> >    Junio C Hamano (19):\n> >       git-merge: make it usable as the first class UI\n> \n> Also very exciting. Please do keep up the user-interface improvements, \n> everybody.\n\nI concur.\n\nCiao,\nDscho\n"}]}