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 :
> 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'
>>
>
On Fri, May 01, 2009 at 06:17:29AM +0100, Colin Adams wrote:
> So after the:
>
> make git-clone
>
> I should do:
>
> cd src
> git checkout DragonFly_RELEASE_2_2
I believe just
make git-clone GIT_BRANCH=DragonFly_RELEASE_2_2
should work, or it should be fixed.
Cheers.
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 :
:But git checkout v2.2.1 was what i actually needed-:)
:
:So what I did was the following (in case whoever maintains the
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 :
>
> :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
: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
r
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):
1) cd /usr
2) make git-clone
3) cd src
4) git tag (to find the label for the next command)
5) git checkout v2.2.1
6) make buildworld
7) make buildkernel
2009/5/1 Colin Adams :
> 2009/5/1 Matthew Dillon :
>> :in /usr or /usr/src?
>>
>> The Makefile to do the source tree management is in /usr. It sets up
>> the GIT repo and checks out the project into /usr/src.
>>
>
> So after the:
>
> make git-clone
>
> I should do:
>
> cd src
> git checkout
