threads / discuss / 6389

Re: What's in git.git and announcing GIT v1.5.0-rc1

Subject: Re: What's in git.git and announcing GIT v1.5.0-rc1

## tl;dr

3 messages between Jan 15, 2007 and Jan 15, 2007.

replies: 2people: 3as markdown or json

Horst H. von Brand· Jan 15, 2007, 02:21 UTC · lore

lamikr <lamikr@cc.jyu.fi> wrote:

Show 22 quoted lines

> Junio C Hamano wrote:
> > The tip of 'master' branch is tagged as v1.5.0-rc1; this means a
> > few things:
> >   
> Hi
> 
> Would it make sense to add something like this to the announcements as
> it is not very easy to find references to the git-repository itself from
> the net.
> 
>    You can get the git repository-itself by using a following commands
> 
>            git-clone git://git.kernel.org/pub/scm/git/git.git git_repo
> 
>    After that you can switch to tagged version <v1.5.0-rc1> or sources
> from the repository by using command
> 
>           git-checkout -f v1.5.0-rc1 master
> 
>    Alternatively you can download the tar packed version of sources from
>       
>           http://www.kernel.org/pub/software/scm/git/

Be careful, this gives you a old-fashioned repository, the repositories created by 1.5.0-rc are different, and 1.4.4.4 doesn't grok them:

   * refusing to create funny ref 'remotes/origin/*' locally

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                    Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria             +56 32 2654239
Casilla 110-V, Valparaiso, Chile               Fax:  +56 32 2797513

lamikr· Jan 15, 2007, 20:54 UTC · re: Horst H. von Brand · lore

Show 23 quoted lines

>> Would it make sense to add something like this to the announcements as
>> it is not very easy to find references to the git-repository itself from
>> the net.
>>
>>    You can get the git repository-itself by using a following commands
>>
>>            git-clone git://git.kernel.org/pub/scm/git/git.git git_repo
>>
>>    After that you can switch to tagged version <v1.5.0-rc1> or sources
>> from the repository by using command
>>
>>           git-checkout -f v1.5.0-rc1 master
>>
>>    Alternatively you can download the tar packed version of sources from
>>       
>>           http://www.kernel.org/pub/software/scm/git/
>>     
>
> Be careful, this gives you a old-fashioned repository, the repositories
> created by 1.5.0-rc are different, and 1.4.4.4 doesn't grok them:
>
>    * refusing to create funny ref 'remotes/origin/*' locally
>

So that would also not work if one uses git-1.4.4 client for fetching from the git-1.5.x repository? How one is then supposed to jump from head/master to tagged version?

Mika

Junio C Hamano· Jan 15, 2007, 21:56 UTC · re: lamikr · lore

lamikr <lamikr@cc.jyu.fi> writes:

Show 7 quoted lines

>> Be careful, this gives you a old-fashioned repository, the repositories
>> created by 1.5.0-rc are different, and 1.4.4.4 doesn't grok them:
>>
>>    * refusing to create funny ref 'remotes/origin/*' locally
>>   
> So that would also not work if one uses git-1.4.4 client for fetching
> from the git-1.5.x repository?

That is untrue. You do not care (nor you would not generally be even to tell) which version the repository at the remote end was prepared with when cloning or fetching from a remote git repository.

A new repository created by 'git-clone' in 1.5.0 will create the repository with default configuration that uses a new feature to allow all (present or future) remote branches tracked.

The feature is "refspec wildcard" and looks like this:

	[remote "origin"]
        fetch = +refs/heads/*:refs/remotes/origin/*

1.4.4 and older do not understand this new feature used in the configuration, so if you create a new repository by running 1.5.0 clone, you would need to futz with the configuration file if we want to use that repository with 1.4.4; you would need to specify the branches you would want individually:

	[remote "origin"]
        fetch = +refs/heads/master:refs/remotes/origin/master
        fetch = +refs/heads/next:refs/remotes/origin/next

Even if you are updating to 1.5.0, if you will never be interested in some of the remote branches, the above to exclude unwanted ones is a good trick to know.