{"thread":{"id":"3010","subject":"[ANNOUCNE] GIT 1.1.0","startedAt":"2006-01-09T01:20:49Z","lastAt":"2006-01-11T09:25:00Z","messageCount":16,"participants":["Junio C Hamano","Coywolf Qi Hunt","Martin Langhoff","lamikr","Andreas Ericsson","H. Peter Anvin","Johannes Schindelin","Gerrit Pape"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14330","messageId":"7v4q4eurgu.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":null,"subject":"[ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-09T01:20:49Z","receivedAt":"2006-01-09T01:20:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest feature release GIT 1.1.0 is available at the usual places:\n\n\thttp://www.kernel.org/pub/software/scm/git/\n\n\tgit-1.1.0.tar.{gz,bz2}\t\t\t(tarball)\n\tRPMS/$arch/git-*-1.1.0-1.$arch.rpm\t(RPM)\n\nThis contains all the fixes present in 1.0.8, with the following\nenhancements:\n\n - \"git clone -o $name\" can name a branch other than \"origin\" to\n   be used to keep track of upstream (Johannes).\n\n - Easier shared repository setup (Johannes).\n\n - \"git describe\" command (Linus).\n\n - \"git --version\" from an interim snapshot gives a more\n   descriptive version name than \"1.0-GIT\" (Linus).\n\n - \"git whatchanged\" shows abbreviated object names by default.\n\n - \"git checkout -- paths\" and \"git checkout treeish paths\" use\n   cwd relative pathname and work from a subdirectory.\n\n - \"git checkout [-b newbranch] branch\" works from a\n   subdirectory and works on the entire tree.\n\n - \"git ls-tree\" shows cwd relative pathnames by default; full\n   pathnames can be obtained with --full-name, just like \"git\n   ls-files\" (Linus and me).\n\n - \"git send-pack\" and \"git push\" notice when the remote end\n   refuses to update a ref (e.g. hooks/update) and exits with an\n   error.  This hopefully would help Cogito as well.\n\n - \"git fetch\" and \"git pull\" automatically follows remote tags\n   while tracking branches.\n\n - \"git ls-files --others\" can be used with \"--directory\" option\n   to omit the contents of directories without any tracked file\n   but instead to show the directories themselves (Linus).  \"git\n   status\" uses this to unclutter \"Untracked files\" section.\n\n - Optimized \"git pack-redundant\" (Lukas).\n\n - \"git daemon --base-path=/pub/git\" can reroot the directory\n   tree exposed to the outside world, similar to DOCUMENT_ROOT\n   (Pasky).\n\n - \"git cherry\" can be told not to show everything we have (Yann\n   Dirson).\n\n - git URL can use [IPv6address/IPvFuture] literal addresses\n   (Hideaki).\n"},{"id":"14351","messageId":"20060109084930.GA560@localhost.localdomain","threadId":"3010","inReplyTo":"7v4q4eurgu.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Coywolf Qi Hunt","fromEmail":"qiyong@fc-cn.com","sentAt":"2006-01-09T08:49:30Z","receivedAt":"2006-01-09T08:49:30Z","isPatch":false,"sender":{"key":"qiyong@fc-cn.com","avatar":null},"body":"On Sun, Jan 08, 2006 at 05:20:49PM -0800, Junio C Hamano wrote:\n> The latest feature release GIT 1.1.0 is available at the usual places:\n> \n> \thttp://www.kernel.org/pub/software/scm/git/\n> \n> \tgit-1.1.0.tar.{gz,bz2}\t\t\t(tarball)\n> \tRPMS/$arch/git-*-1.1.0-1.$arch.rpm\t(RPM)\n\nWhy not support debian? I see the debian directory is outdated.\n-- \nCoywolf Qi Hunt\n"},{"id":"14355","messageId":"7vr77hpwla.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":"20060109084930.GA560@localhost.localdomain","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-09T09:41:21Z","receivedAt":"2006-01-09T09:41:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Coywolf Qi Hunt <qiyong@fc-cn.com> writes:\n\n> Why not support debian? I see the debian directory is outdated.\n\nI think that was discussed already this year, so look in the\nlist archive for the past 10 days or so please before asking.\n"},{"id":"14357","messageId":"7vbqylpty1.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":"7vr77hpwla.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-09T10:38:30Z","receivedAt":"2006-01-09T10:38:30Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano <junkio@cox.net> writes:\n\n> Coywolf Qi Hunt <qiyong@fc-cn.com> writes:\n>\n>> Why not support debian? I see the debian directory is outdated.\n>\n> I think that was discussed already this year, so look in the\n> list archive for the past 10 days or so please before asking.\n\nEspecially, please see this thread:\n\n    http://marc.theaimsgroup.com/?l=git&m=113576889301331 \n\nI haven't received any patches to re-add debian/ directory from\nGerrit since I removed it, and I do not expect nor wish to get\none.  I respect Gerrit's request not to ship debian/ directory\nmyself.\n\nIf you want to see deb packages at kernel.org built by me, you\nneed to convince both Gerrit and me with a workable workflow\nthat does not add extra burden on us and avoids confusion.\n\nA starting point might be for me to slave debian/ part from\nGerrit, updating debian/changelog with only X.Y.Z-0 entries by\nme, and publish X.Y.Z-0 packages at kernel.org.\n"},{"id":"14358","messageId":"46a038f90601090309h734ebd8at4b5925f5661edbf4@mail.gmail.com","threadId":"3010","inReplyTo":"7vbqylpty1.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2006-01-09T11:09:29Z","receivedAt":"2006-01-09T11:09:29Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 1/9/06, Junio C Hamano <junkio@cox.net> wrote:\n> > I think that was discussed already this year, so look in the\n> > list archive for the past 10 days or so please before asking.\n\nLike, yesterday ;-)\n\nAnyway, I have to report that I'm now a happy backports.org user for\nall the git-core packages on my production servers. And sid has your\ngit-core fix too, if you happen to be feeling unstable.\n\nMany thanks to Gerrit and whoever's done the backports.org one.\n\n\nmartin\n"},{"id":"14363","messageId":"43C2CAED.8030304@cc.jyu.fi","threadId":"3010","inReplyTo":"7v4q4eurgu.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"lamikr","fromEmail":"lamikr@cc.jyu.fi","sentAt":"2006-01-09T20:43:25Z","receivedAt":"2006-01-09T20:43:25Z","isPatch":false,"sender":{"key":"lamikr@cc.jyu.fi","avatar":null},"body":"\n> - \"git --version\" from an interim snapshot gives a more\n>   descriptive version name than \"1.0-GIT\" (Linus).\n>  \n>\nI installed 1.1.0 today and it shows me\n\n$ git --version\ngit version 1.0.GIT\n\nMika\n"},{"id":"14364","messageId":"43C2E230.1000107@op5.se","threadId":"3010","inReplyTo":"43C2CAED.8030304@cc.jyu.fi","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2006-01-09T22:22:40Z","receivedAt":"2006-01-09T22:22:40Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"lamikr wrote:\n>>- \"git --version\" from an interim snapshot gives a more\n>>  descriptive version name than \"1.0-GIT\" (Linus).\n>> \n>>\n> \n> I installed 1.1.0 today and it shows me\n> \n> $ git --version\n> git version 1.0.GIT\n> \n\nYou did not have git-describe installed prior to building 1.1.0. If you \nre-install right on top the one you did today the version-file will be \ngenerated correctly.\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\nTel: +46 8-230225                  Fax: +46 8-230231\n"},{"id":"14369","messageId":"7vwth9f1nk.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":"43C2CAED.8030304@cc.jyu.fi","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-09T22:59:43Z","receivedAt":"2006-01-09T22:59:43Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"lamikr <lamikr@cc.jyu.fi> writes:\n\n>> - \"git --version\" from an interim snapshot gives a more\n>>   descriptive version name than \"1.0-GIT\" (Linus).\n>>  \n>>\n> I installed 1.1.0 today and it shows me\n>\n> $ git --version\n> git version 1.0.GIT\n\nAh, sorry, and thanks for catching this.  RPM building procedure\nis somewhat tricky, and I failed to catch this bug.  Fixed in my\ntree --- this calls for an early 1.1.1 release I guess.\n\nOn the other hand, if you are building from the source, what\nAndreas said applies, and in addition you need to fetch v1.1.0\ntag before building; otherwise the versioning mechanism would not\nnotice you are building v1.1.0.\n"},{"id":"14378","messageId":"43C2F7E2.4090909@cc.jyu.fi","threadId":"3010","inReplyTo":"7vwth9f1nk.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"lamikr","fromEmail":"lamikr@cc.jyu.fi","sentAt":"2006-01-09T23:55:14Z","receivedAt":"2006-01-09T23:55:14Z","isPatch":false,"sender":{"key":"lamikr@cc.jyu.fi","avatar":null},"body":"\n>Ah, sorry, and thanks for catching this.  RPM building procedure\n>is somewhat tricky, and I failed to catch this bug.  Fixed in my\n>tree --- this calls for an early 1.1.1 release I guess.\n>\n>On the other hand, if you are building from the source, what\n>Andreas said applies, and in addition you need to fetch v1.1.0\n>tag before building; otherwise the versioning mechanism would not\n>notice you are building v1.1.0.\n>  \n>\nI was not using git for fetching git sources,\nI have build from the git 1.1.0.tar.bz2.\n\nDid you mean that things should work after 1.1.1 is released?\nI tried to fresh build and install of 1.1.0 on top of the previous\n1.1.0 build but \"git --version\" is still displaying me \"git version 1.0.GIT\"\n\nMika\n"},{"id":"14379","messageId":"43C2FE4A.50203@op5.se","threadId":"3010","inReplyTo":"43C2F7E2.4090909@cc.jyu.fi","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2006-01-10T00:22:34Z","receivedAt":"2006-01-10T00:22:34Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"lamikr wrote:\n>>Ah, sorry, and thanks for catching this.  RPM building procedure\n>>is somewhat tricky, and I failed to catch this bug.  Fixed in my\n>>tree --- this calls for an early 1.1.1 release I guess.\n>>\n>>On the other hand, if you are building from the source, what\n>>Andreas said applies, and in addition you need to fetch v1.1.0\n>>tag before building; otherwise the versioning mechanism would not\n>>notice you are building v1.1.0.\n>> \n>>\n> \n> I was not using git for fetching git sources,\n> I have build from the git 1.1.0.tar.bz2.\n> \n> Did you mean that things should work after 1.1.1 is released?\n\n\nNot unless you build from the git-repo, no.\n\nSnapshots will fail to set the \"proper\" version every time, because the \nGIT-VERSION-FILE: is a forced target and even if git-describe is present \nit will find neither tags nor HEAD.\n\nI have no solution to this, apart from rewriting the Makefile on the fly \nwhenever a release tarball is created.\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\nTel: +46 8-230225                  Fax: +46 8-230231\n"},{"id":"14380","messageId":"7v7j99exkc.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":"43C2F7E2.4090909@cc.jyu.fi","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-10T00:28:03Z","receivedAt":"2006-01-10T00:28:03Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"lamikr <lamikr@cc.jyu.fi> writes:\n\n> Did you mean that things should work after 1.1.1 is released?\n> I tried to fresh build and install of 1.1.0 on top of the previous\n> 1.1.0 build but \"git --version\" is still displaying me \"git version 1.0.GIT\"\n\nYou need to build from a git repository for these automated\nversion numbers to work, and this will *not* change post 1.1.1.\n\nBut with the patch I sent out earlier, you should be able to:\n\n\t$ VN=1.1.1 make\n\nin a non-git repository (e.g. an untarred directory from a\ntarball).  What the patch fixes is to fix it for RPM binary\npackages.\n\nI expect that people building from the source do so from a git\nrepository not from a tarball, except when bootstrapping, so\nhopefully this should not be too much of a problem.\n"},{"id":"14381","messageId":"7v1wzgg9nm.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":"43C2FE4A.50203@op5.se","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-10T01:21:33Z","receivedAt":"2006-01-10T01:21:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andreas Ericsson <ae@op5.se> writes:\n\n> I have no solution to this, apart from rewriting the Makefile on the\n> fly whenever a release tarball is created.\n\nWell, there is always an option to update the fallback version\nnumber hardcoded in GIT-VERSION-GEN script, but that kind fo\ndefeats the whole idea of the current setup, so...\n"},{"id":"14382","messageId":"43C31551.5010202@zytor.com","threadId":"3010","inReplyTo":"7v7j99exkc.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2006-01-10T02:00:49Z","receivedAt":"2006-01-10T02:00:49Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Junio C Hamano wrote:\n> lamikr <lamikr@cc.jyu.fi> writes:\n> \n>>Did you mean that things should work after 1.1.1 is released?\n>>I tried to fresh build and install of 1.1.0 on top of the previous\n>>1.1.0 build but \"git --version\" is still displaying me \"git version 1.0.GIT\"\n> \n> You need to build from a git repository for these automated\n> version numbers to work, and this will *not* change post 1.1.1.\n> \n\nTarballs really should work as-is... the easy way to deal with that is \nto have the tarball make script generate a version file which isn't part \nof the git tree.\n\nI'll send a patch under a separate cover.\n\n\t-hpa\n"},{"id":"14390","messageId":"7vzmm4aijx.fsf@assigned-by-dhcp.cox.net","threadId":"3010","inReplyTo":"43C31551.5010202@zytor.com","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-01-10T03:05:54Z","receivedAt":"2006-01-10T03:05:54Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"H. Peter Anvin\" <hpa@zytor.com> writes:\n\n> Tarballs really should work as-is... the easy way to deal with that is\n> to have the tarball make script generate a version file which isn't\n> part of the git tree.\n>\n> I'll send a patch under a separate cover.\n\nThanks.\n"},{"id":"14407","messageId":"Pine.LNX.4.63.0601101540070.26054@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"3010","inReplyTo":"7v1wzgg9nm.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-01-10T14:49:04Z","receivedAt":"2006-01-10T14:49:04Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 9 Jan 2006, Junio C Hamano wrote:\n\n> Andreas Ericsson <ae@op5.se> writes:\n> \n> > I have no solution to this, apart from rewriting the Makefile on the\n> > fly whenever a release tarball is created.\n> \n> Well, there is always an option to update the fallback version\n> number hardcoded in GIT-VERSION-GEN script, but that kind fo\n> defeats the whole idea of the current setup, so...\n\nThe whole idea of the current setup is working only if you have a git \nrepository of git. Kind of a chicken-egg, right?\n\nSo, why not just include GIT-VERSION-FILE in the tarball, and let \nGIT-VERSION-GEN check if there exists .git or $GIT_DIR before trying its \nvoodoo?\n\n---\n\ndiff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN\nindex 845b9dc..b65b214 100755\n--- a/GIT-VERSION-GEN\n+++ b/GIT-VERSION-GEN\n@@ -2,6 +2,9 @@\n \n GVF=GIT-VERSION-FILE\n \n+test -z \"$GIT_DIR\" && GIT_DIR=.git\n+test -d \"$GIT_DIR\" || exit 0\n+\n VN=$(git-describe --abbrev=4 HEAD 2>/dev/null) || VN=v1.0.GIT\n VN=$(expr \"$VN\" : v'\\(.*\\)')\n if test -r $GVF\n"},{"id":"14470","messageId":"20060111092500.6041.qmail@6aae66343b5940.315fe32.mid.smarden.org","threadId":"3010","inReplyTo":"7vbqylpty1.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUCNE] GIT 1.1.0","fromName":"Gerrit Pape","fromEmail":"pape@smarden.org","sentAt":"2006-01-11T09:25:00Z","receivedAt":"2006-01-11T09:25:00Z","isPatch":false,"sender":{"key":"pape@smarden.org","avatar":"https://avatars.githubusercontent.com/u/143170252?v=4"},"body":"On Mon, Jan 09, 2006 at 02:38:30AM -0800, Junio C Hamano wrote:\n> Junio C Hamano <junkio@cox.net> writes:\n> > Coywolf Qi Hunt <qiyong@fc-cn.com> writes:\n> >> Why not support debian? I see the debian directory is outdated.\n> >\n> > I think that was discussed already this year, so look in the\n> > list archive for the past 10 days or so please before asking.\n> \n> Especially, please see this thread:\n> \n>     http://marc.theaimsgroup.com/?l=git&m=113576889301331 \n> \n> I haven't received any patches to re-add debian/ directory from\n> Gerrit since I removed it, and I do not expect nor wish to get\n> one.  I respect Gerrit's request not to ship debian/ directory\n> myself.\n\nThanks.  \n\n> If you want to see deb packages at kernel.org built by me, you\n> need to convince both Gerrit and me with a workable workflow\n> that does not add extra burden on us and avoids confusion.\n\nI'm afraid, I can't always keep up with the git development speed.  So\nit's quite possible that a debian/ directory in the git repository gets\ntemporarily outdated and possibly broken, and I'm not available to\nupdate immediately.\n\nStarting with version 1.0.8-1, this should work if you want to build\nDebian packages on sid or sarge from the maint or master branch (or the\nv1.1.1 tag) yourself:\n\n $ git checkout maint\n $ wget -q -O- http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.0.8-1.diff.gz |\n gunzip |patch -p1\n patching file debian/changelog\n patching file debian/control\n patching file debian/copyright\n patching file debian/rules\n patching file debian/git-core.docs\n patching file debian/git-doc.docs\n patching file debian/implicit\n patching file debian/git-core.postinst\n patching file debian/git-core.prerm\n $ chmod 755 debian/rules\n $ debchange -v 1.1.1-0.maint20060111 'git maint 20060111'\n $ dpkg-buildpackage -b -rfakeroot -uc -us\n [...]\n $ \n \nHTH, Gerrit.\n"}]}