From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-4.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id CCCC26F546; Mon, 20 Jun 2022 12:05:20 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 496) id 6F5ED6F580; Mon, 20 Jun 2022 12:05:18 +0000 (UTC) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by atuin.qyliss.net (Postfix) with ESMTPS id 19FF56F4FF for ; Mon, 20 Jun 2022 12:05:15 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 93E125C01C4; Mon, 20 Jun 2022 08:05:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 20 Jun 2022 08:05:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1655726712; x=1655813112; bh=nTI/3piC3/ ZYKgg5Ove9M5pg5sGbJsZ/a0K3D7gfCig=; b=sahO3bOY4u2kajkp+94k8d+3PT ofD2P9lDQzPN+injiYQtdOfak720jhWBZg8KrXuSpEh9VOAOP/ypm3U1rBZ0oBOD Rz99q5MKzNUmudR+JaugdAIVbpLNp/aecBWOhm8qu4ItYuYq3zYSVf4rG6VAc6RX lUbHisZeaBIT2AWtyo8kvhGqIh4fUTboGA9IiiUvWxwu9WELsBbkVRVqEAXR0GaC m6BmvkYnDRYiPjzNgE7ipXn+opzdvg+xbZJcOMIAJ9IMZEjnz0DAI9OZQtmo3a1m NqqTKRSCUZ5gETYp2AoKAe27zM1mAEUKaOuRVDARdEU37Rgjj8TM3xDWFDMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1655726712; x=1655813112; bh=nTI/3piC3/ZYKgg5Ove9M5pg5sGb JsZ/a0K3D7gfCig=; b=bvaOJV/ehdxF6t85RmjuulK4Jy7ttD6qlNGHZCInr+Y0 f1g06KoiofY+BJL/Pptor2mYLvlFPUUzxTAHBVLNoaYeyXR3hj5WVUxVqf2ioZjR SQ1T53DRidvrsD7t2RzfU4nc6l+sunf5NbvZBDia6RWOMYXEMNrSb4P/wmsxKDYO 6yX1iD2WeNSXuHfBC7DHZiViqgUhMxI3gTJVPdWPG8IOGOPI3chk7VuHlKP0a6JO gsRwHEQcyI4rvO7EQ6HblZ0hikL5znKVDBzRJ7gabrBgoJP2ZY2K16HECW0jTBGb IUMUDoiKrLXBJVSl4ywrggZi+RFy9jK1zrpmxjy38Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudefuddggeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesghdtreertddtvdenucfhrhhomheptehlhihs shgrucftohhsshcuoehhihesrghlhihsshgrrdhisheqnecuggftrfgrthhtvghrnhepvd egieefffekjefhvdfhtdffleetheejleeuhefhvdduieeuueegueejgfdttedvnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepqhihlhhishhsse gvvhgvrdhqhihlihhsshdrnhgvth X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Jun 2022 08:05:12 -0400 (EDT) Received: by eve.qyliss.net (Postfix, from userid 1000) id EBCF436F; Mon, 20 Jun 2022 12:05:09 +0000 (UTC) Date: Mon, 20 Jun 2022 12:05:09 +0000 From: Alyssa Ross To: Ville Ilvonen Subject: Re: Workflow preferences - case aarch64 support Message-ID: <20220620120509.w5j24q6ycj44vwah@eve> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gggodbnlgfycw6wh" Content-Disposition: inline In-Reply-To: Message-ID-Hash: TSGEOJENLHDECZVTNLVIIMV5O32JLGRC X-Message-ID-Hash: TSGEOJENLHDECZVTNLVIIMV5O32JLGRC X-MailFrom: qyliss@eve.qyliss.net X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; header-match-discuss.spectrum-os.org-0; header-match-discuss.spectrum-os.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: discuss@spectrum-os.org X-Mailman-Version: 3.3.5 Precedence: list List-Id: General high-level discussion about Spectrum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --gggodbnlgfycw6wh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 20, 2022 at 01:29:49PM +0300, Ville Ilvonen wrote: > Hi all, > > Good news is that the work on aarch64 support has progressed to the point= where > the Spectrum host can be built natively and run on aarch64 HW. This is excellent! Very exciting. > It's still a bunch of patches in various stages of WIP or review to > spectrum or further > up the stream. > > In short, to "nixpkgs-spectrum": > 0001-Allow-static-building-of-dtc.patch > 0002-Workaround-ld-script-segmentation-fault.patch /* may be not needed */ > 0003-Add-imx8-specific-kernel.patch > and to "spectrum": > 0001-Add-imx8-kernel.patch > > Should anyone want to reproduce, please let me know and I'll try to > find a solution > to share them. Probably worth waiting for cross-compilation support unles= s you > have powerful aarch64 at your disposal. > > In the meanwhile, we try to establish a mechanism to collaborate in branc= hes of > required upstream repos. It's fairly impractical to fork > "nixpkgs-spectrum"-repo due to > its' size, over 2GB, > > Which takes me to the discussion point - what's the workflow proposal > on multiple people > working on the same functionality in the same branch? If I'm not > mistaken the email workflow > creates a new branch for each author? Then someone would have to > cherry-pick them to the > same branch to integrate them in dev time hydra builds. For that situation, I would recommend having a shared Nixpkgs repository where the people working on the change can work on it together. You're right that Nixpkgs is big, but the bulk of it only has to be pushed once, and from that point changes will be incremental. Public git hosts, if you wanted to use one of those, likely already have somebody's copy of Nixpkgs on them and might deduplicate against it, so possibly won't need most git objects to be uploaded anyway. This is broadly how feature development works for other projects using similar workflows, like Linux or QEMU. When it's time to submit the patches to the list for review, anybody can do that. Authorship information is preserved in the patch metadata, so it's fine for one person to submit a patch series that includes patches =66rom multiple authors. git-send-email will also handle automatically CCing authors on patches that they wrote, so questions / review should still find their way to the right person. Does that all make sense? --gggodbnlgfycw6wh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEH9wgcxqlHM/ARR3h+dvtSFmyccAFAmKwYmUACgkQ+dvtSFmy ccA6Yw//Ve6vK8AVbpkCbtFff7Zdk86kAVozUA+lGwSGYTuHOmm5X60RFuKpd6v1 uwMj1e/2x7XUOaqt1LbzE+EBLrVY7IcZCsy7Pdvju9oDWK8kJMX2p5vgsieF0I3w iLw0u6NFJBNnBl7nzKlYWkUMHJVUUmYqf0WmwzI5i7EOQQ5M6L8XNzdTO5UYcKej gdeAncJC9Z99HTunlL1/ygyLBGbD2TXFRbPkQlLspfEdUYWGAb2R321CLCFPZF2g a/9ematcQsXuqKzzdNSfqrPSShjuqgkKZJqyaLY54J3X6loV4rRN43iDdaYi1tDS H4DL0IOdSpbrtqO5OIzU7AaZ0ZPqD6x4tatOkOTUIlmah3dHu3PrnUfKXAAlbGsQ IDezssW5i+TKDWyc2s3zMnxMdqd6GrB4VEhZxXFvpSjakZCWpQksGZdVq1yTFVXC QZTmYycq2qbAdNaDX8x3FDlxI+Ue7ZlwqhxLaRE37dY/jqeADTWBqJMq5L2SLh4V 4381tvDAkHO9s0T5KTHKpaKoxD8b6khJKp37HZ7K+Ah5E+O/keAryEubyM7K3hrU EfpbVjx9pV0/ayRJhMZLl2IaPDGLf/+Ve3rxcaG0G/Dc4G+q4+HaCMXHEUbDD0C7 yEkpF1FeI03TwfPRsW4deRgUGlsaaoBlcO8VwQodkP9BGhZereI= =96HP -----END PGP SIGNATURE----- --gggodbnlgfycw6wh--