Re: DragonFly 2.2.1 released!

[Colin Adams <colinpauladams@xxxxxxxxxxxxxx>]

That works, thanks.

But I think it's time to read the git documentation, to be sure I know
what's going on.

2009/5/1 Jordan Gordeev <jgordeev@dir.bg>:
> Colin Adams wrote:
>>
>> I still get the error message (on the git branch command, this time):
>>
>> fatal: Not a valid oblect name: 'DragonFly_RELEASE_2_2'
>>
>> 2009/5/1 Matthew Dillon <dillon@apollo.backplane.com>:
>>
>>>
>>> :But git checkout v2.2.1 was what i actually needed-:)
>>> :
>>> :So what I did was the following (in case whoever maintains the wiki
>>> :page is interested):
>>>
>>>   2.2.1 will not track additional changes made to the 2.2.x branch
>>>   though.
>>>
>>>   Maybe what is missing here is a local branch to track the
>>>   remote branch.
>>>
>>>   Try this:
>>>
>>>   git branch origin/DragonFly_RELEASE_2_2 DragonFly_RELEASE_2_2
>>>   git checkout DragonFly_RELEASE_2_2
>>>
>>> :What I'm not clear about is if I need to do anything with pkgsrc. My
>>> :guess is that applications shouldn't care what the X is in kernel
>>> :version 2.2.X.
>>>
>>>   Everything in the 2.2.x series uses the same package set.
>>>
>>>   The main development branch (2.3.x) bumped the major version on libc
>>>   which means all major packages would need to be recompiled, so I
>>>   recommend sticking with the 2.2.x series for now.
>>>
>>>                                       -Matt
>>>
>>>
>
> Use "git branch DragonFly_RELEASE_2_2 origin/DragonFly_RELEASE_2_2", i.e.
> reverse the arguments.
>
>