From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail.oboj.net ([195.178.185.14]) by ewsd; Sat Jan  4 16:34:03 EST 2020
Received: from localhost (localhost [127.0.0.1])
	by mail.oboj.net (Postfix) with ESMTP id 7AAEBBECC78;
	Sat,  4 Jan 2020 22:33:55 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mail.oboj.net
Received: from mail.oboj.net ([127.0.0.1])
	by localhost (mail.oboj.net [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qiAglLqWryQQ; Sat,  4 Jan 2020 22:33:49 +0100 (CET)
Received: from www.oboj.net (unknown [195.178.185.23])
	by mail.oboj.net (Postfix) with ESMTP id D5F0CBECC77;
	Sat,  4 Jan 2020 22:33:48 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Sat, 04 Jan 2020 23:33:48 +0200
From: jamos@oboj.net
To: 9front@9front.org
Cc: ori@eigenstate.org
Subject: Re: [9front] Netsurf 3.9 for Plan 9 (work in progress)
In-Reply-To: <7EA616C7FF07CA423F342D0FFDF55539@eigenstate.org>
References: <7EA616C7FF07CA423F342D0FFDF55539@eigenstate.org>
Message-ID: <0d0c66a3d67f051752a3d82ea1190304@oboj.net>
X-Sender: jamos@oboj.net
User-Agent: Roundcube Webmail/1.3.4
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: stateless basic engine SOAP table hosting 

On 2020-01-04 19:14, ori@eigenstate.org wrote:

> 
> What I'd do is clone the upstream netsurf repos onto any git host
> that you feel like (except gitlab -- git9 triggers a bug in their
> backend, and I haven't had time to find a workaround), and then
> branch off a 'plan9' branch that we can work on, and commit the
> current state.

That sounds like a cool way, but I am kind of a git rookie. I assume 
that the reason to clone the main repository is that it will be easier 
to merge them together eventually? Or even to keep the plan 9 branch up 
to date with new versions of the mainline? I have based my port on the 
stable release 3.9 while the core team is happily hacking away on what 
even will be the next release (usually one version per year).

The official site has many git repositories 
(https://source.netsurf-browser.org) - from which I actually downloaded 
every support library separately. Each repository has a tag for each 
release. There are also a number of branches (especially for the main 
netsurf repository: 
https://source.netsurf-browser.org/netsurf.git/refs/heads) that looks 
like experiments.

I might be inclined to keep it simple to begin with, but if there are 
very compelling reasons for a more elaborate way, I might be open to 
that, in order to avoid lots of work later on.