[haiku] [haiku-development] Re: Re: R1/beta1: Here We Go (at last)
- From: "Thomas Mueller" <mueller6723@xxxxxxx>
- To: Haiku ML <haiku@xxxxxxxxxxxxx>, Haiku Development ML <haiku-development@xxxxxxxxxxxxx>
- Date: Tue, 28 Aug 2018 17:54:38 +0000
28 aoÃ»t 2018 10:26 "Thomas Mueller" <mueller6723@xxxxxxx> a Ã©crit:
What happens to the git tree structure on Github (haikuports,
haikuports.cross and haikuporter) and
on git.haiku-os.org (haiku and buildtools)?
Nothing special. Git knows how to manage branches as branches, not as
directories like svn.
$ git pull
error: wrong index v2 file size in
Your git checkout seems corrupt?
Anyways, you should be getting sources from https://review.haiku-os.org/haiku
as mentionned in
I didn't see any special notice of the branch on git.haiku-os.org web
interface, but I guess it was
too early and you didn't get that far yet.
It's there: https://git.haiku-os.org/haiku/?h=r1beta1
I tried again with the same "git pull" and was successful. Maybe something was
in a transitional state when I tried earlier and got the error.
Did the git repository change from git.haiku-os.org to review.haiku-os.org ?
When I clicked that link from
I got Not Found
Now I don't know whether to stay with git.haiku-os.org or switch to
review.haiku-os.org , for haiku and buildtools.
I noticed the new version tag r1beta1.
Could I keep up with both r1beta1 and pre_beta2 or however that would be noted,
and keep the two branches sufficiently separate at my end that I and the build
tools would know which one I was compiling?
I suppose there will be no branch change for buildtools, or for haikuports,
haikuports.cross and haikuporter on Github?
Other related posts: