From owner-freebsd-hackers@freebsd.org Thu Sep 3 13:34:37 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E37173E6742 for ; Thu, 3 Sep 2020 13:34:37 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from trac.mcusim.org (trac.mcusim.org [176.58.93.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bj1xn0cSzz4RKV; Thu, 3 Sep 2020 13:34:36 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from ds-laptop (unknown [83.26.189.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by trac.mcusim.org (Postfix) with ESMTPSA id B05BC7B7B7; Thu, 3 Sep 2020 15:34:34 +0200 (CEST) Date: Thu, 3 Sep 2020 15:34:32 +0200 From: Dmitry Salychev To: Stefan Esser Cc: freebsd-hackers@freebsd.org Subject: Re: Tracking FreeBSD-CURRENT Message-ID: <20200903133432.GC24815@ds-laptop> References: <20200903071401.GA24815@ds-laptop> <6ea7df0a-f62f-d4b4-da88-cc7d96635fc4@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6ea7df0a-f62f-d4b4-da88-cc7d96635fc4@freebsd.org> User-Agent: Unknown/0.75.1 X-Rspamd-Queue-Id: 4Bj1xn0cSzz4RKV X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.78 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[83.26.189.68:received]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.002]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; NEURAL_HAM_SHORT(-0.49)[-0.490]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[mcusim.org,reject]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:176.58.93.0/24, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Sep 2020 13:34:37 -0000 Hi Stefan, > Any new code must be committed to -CURRENT first, before it may be > merged into the stable branches (and then will make it into a release). Is this approach the same for code which is intended for ARM? For example, if there is a driver for an ethernet transceiver connected to BeagleBone Black. I should track -CURRENT on my laptop, add, build and test my driver on BBB, merge the latest changes from -CURRENT and send a patch. Am I correct? > Since -CURRENT makes no guarantees with regard to kernel interfaces > and data structures, there is a small risk, that you'll have to adopt > to changes between when you "froze" your -CURRENT source tree and the > tree at the time of commit. > > Staying current is not much of a problem, though. On my system, the > "svn up" of the -CURRENT source tree generally finishes in less than > 10 seconds and "make buildworld" takes only a few minutes, if you > enable META_MODE - and if there are any collisions you'll notice > them just when the conflicting changes are fresh and it is easy to > assess what needs to be done to adapt your code. It looks like I'd better to have a spare disk for my experiments to track -CURRENT. > Definitely not, and I know that some developers fork -CURRENT at > some suitable point and merge from the official repository only every > few weeks. > > This will obviously not be a good approach, if you are working with > data structures that are in the process of being significantly modified, > e.g. to improve the scale-ability of the filesystem or network code. It shouldn't be a problem because I'd like to program a driver for Microchip's KSZ9563R (eth switch) which I might only be interested in :) Thanks for your help! Regards, Dmitry