{"thread":{"id":"6389","subject":"Re: What's in git.git and announcing GIT v1.5.0-rc1","startedAt":"2007-01-15T02:21:47Z","lastAt":"2007-01-15T21:56:07Z","messageCount":3,"participants":["Horst H. von Brand","lamikr","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"31755","messageId":"200701150221.l0F2LlwJ016982@laptop13.inf.utfsm.cl","threadId":"6389","inReplyTo":"lamikr@cc.jyu.fi","subject":"Re: What's in git.git and announcing GIT v1.5.0-rc1","fromName":"Horst H. von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2007-01-15T02:21:47Z","receivedAt":"2007-01-15T02:21:47Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"lamikr <lamikr@cc.jyu.fi> wrote:\n> Junio C Hamano wrote:\n> > The tip of 'master' branch is tagged as v1.5.0-rc1; this means a\n> > few things:\n> >   \n> Hi\n> \n> Would it make sense to add something like this to the announcements as\n> it is not very easy to find references to the git-repository itself from\n> the net.\n> \n>    You can get the git repository-itself by using a following commands\n> \n>            git-clone git://git.kernel.org/pub/scm/git/git.git git_repo\n> \n>    After that you can switch to tagged version <v1.5.0-rc1> or sources\n> from the repository by using command\n> \n>           git-checkout -f v1.5.0-rc1 master\n> \n>    Alternatively you can download the tar packed version of sources from\n>       \n>           http://www.kernel.org/pub/software/scm/git/\n\nBe careful, this gives you a old-fashioned repository, the repositories\ncreated by 1.5.0-rc are different, and 1.4.4.4 doesn't grok them:\n\n   * refusing to create funny ref 'remotes/origin/*' locally\n-- \nDr. Horst H. von Brand                   User #22616 counter.li.org\nDepartamento de Informatica                    Fono: +56 32 2654431\nUniversidad Tecnica Federico Santa Maria             +56 32 2654239\nCasilla 110-V, Valparaiso, Chile               Fax:  +56 32 2797513\n"},{"id":"31765","messageId":"45ABE9FD.4050601@cc.jyu.fi","threadId":"6389","inReplyTo":"200701150221.l0F2LlwJ016982@laptop13.inf.utfsm.cl","subject":"Re: What's in git.git and announcing GIT v1.5.0-rc1","fromName":"lamikr","fromEmail":"lamikr@cc.jyu.fi","sentAt":"2007-01-15T20:54:21Z","receivedAt":"2007-01-15T20:54:21Z","isPatch":false,"sender":{"key":"lamikr@cc.jyu.fi","avatar":null},"body":"\n>> Would it make sense to add something like this to the announcements as\n>> it is not very easy to find references to the git-repository itself from\n>> the net.\n>>\n>>    You can get the git repository-itself by using a following commands\n>>\n>>            git-clone git://git.kernel.org/pub/scm/git/git.git git_repo\n>>\n>>    After that you can switch to tagged version <v1.5.0-rc1> or sources\n>> from the repository by using command\n>>\n>>           git-checkout -f v1.5.0-rc1 master\n>>\n>>    Alternatively you can download the tar packed version of sources from\n>>       \n>>           http://www.kernel.org/pub/software/scm/git/\n>>     \n>\n> Be careful, this gives you a old-fashioned repository, the repositories\n> created by 1.5.0-rc are different, and 1.4.4.4 doesn't grok them:\n>\n>    * refusing to create funny ref 'remotes/origin/*' locally\n>   \nSo that would also not work if one uses git-1.4.4 client for fetching\nfrom the git-1.5.x repository?\nHow one is then supposed to jump from head/master to tagged version?\n\nMika\n"},{"id":"31770","messageId":"7vtzys0xag.fsf@assigned-by-dhcp.cox.net","threadId":"6389","inReplyTo":"45ABE9FD.4050601@cc.jyu.fi","subject":"Re: What's in git.git and announcing GIT v1.5.0-rc1","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-01-15T21:56:07Z","receivedAt":"2007-01-15T21:56:07Z","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>> Be careful, this gives you a old-fashioned repository, the repositories\n>> created by 1.5.0-rc are different, and 1.4.4.4 doesn't grok them:\n>>\n>>    * refusing to create funny ref 'remotes/origin/*' locally\n>>   \n> So that would also not work if one uses git-1.4.4 client for fetching\n> from the git-1.5.x repository?\n\nThat is untrue.  You do not care (nor you would not generally be\neven to tell) which version the repository at the remote end was\nprepared with when cloning or fetching from a remote git\nrepository.\n\nA new repository created by 'git-clone' in 1.5.0 will create the\nrepository with default configuration that uses a new feature to\nallow all (present or future) remote branches tracked.  \n\nThe feature is\n\"refspec wildcard\" and looks like this:\n\n\t[remote \"origin\"]\n        fetch = +refs/heads/*:refs/remotes/origin/*\n\n1.4.4 and older do not understand this new feature used in the\nconfiguration, so if you create a new repository by running\n1.5.0 clone, you would need to futz with the configuration file\nif we want to use that repository with 1.4.4; you would need to\nspecify the branches you would want individually:\n\n\t[remote \"origin\"]\n        fetch = +refs/heads/master:refs/remotes/origin/master\n        fetch = +refs/heads/next:refs/remotes/origin/next\n\nEven if you are updating to 1.5.0, if you will never be\ninterested in some of the remote branches, the above to exclude\nunwanted ones is a good trick to know.\n"}]}