DragonFly users List (threaded) for 2009-05
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
[no subject]
L7074995@apollo.backplane.com> <1afdeaec0905010754w7855ef88vf8dd767b88307143@mail.gmail.com>
From: Jordan Gordeev <jgordeev@dir.bg>
Subject: Re: DragonFly 2.2.1 released!
Date: Fri, 01 May 2009 20:58:58 +0300
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:users@crater.dragonflybsd.org>
List-Subscribe: <mailto:users-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:users-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:users-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-users@crater.dragonflybsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <1afdeaec0905010754w7855ef88vf8dd767b88307143@mail.gmail.com>
Sender: users-errors@crater.dragonflybsd.org
Errors-To: users-errors@crater.dragonflybsd.org
Lines: 39
NNTP-Posting-Host: 216.240.41.25
X-Trace: 1241201623 crater_reader.dragonflybsd.org 882 216.240.41.25
Xref: crater_reader.dragonflybsd.org dragonfly.users:12355
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.
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]