From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 03 Mar 2022 21:36:09 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nPsBF-00GrDE-7o for lore@lore.pengutronix.de; Thu, 03 Mar 2022 21:36:09 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nPsBE-0006Cu-Hy; Thu, 03 Mar 2022 21:36:08 +0100 Received: from mout.kundenserver.de ([217.72.192.74]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nPsAx-0006CT-RI for ptxdist@pengutronix.de; Thu, 03 Mar 2022 21:35:52 +0100 Received: from methusalix.internal.home.lespocky.de ([92.117.58.152]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MJEEf-1nk1Uc1nIp-00Kg8b; Thu, 03 Mar 2022 21:35:49 +0100 Received: from falbala.internal.home.lespocky.de ([192.168.243.94]) by methusalix.internal.home.lespocky.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nPsAp-0007Zo-4y; Thu, 03 Mar 2022 21:35:48 +0100 Date: Thu, 3 Mar 2022 21:35:36 +0100 From: Alexander Dahl To: Christian Melki , ptxdist@pengutronix.de Message-ID: <20220303203533.GC26895@falbala.internal.home.lespocky.de> Mail-Followup-To: Christian Melki , ptxdist@pengutronix.de References: <20220303134028.GN12709@pengutronix.de> <7ee003fb-e6c3-34d7-d9e2-d29279369b0c@t2data.com> <9e421142-d037-6b62-79c4-2a7a9a09d120@benfm.de> <00ae8995-135e-dc67-737e-4c7d6ec3e08a@t2data.com> <20220303201138.GB26895@falbala.internal.home.lespocky.de> MIME-Version: 1.0 In-Reply-To: <20220303201138.GB26895@falbala.internal.home.lespocky.de> X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.10.1 (2018-07-13) X-Scan-Signature: cf2f60a981f44e92cdf3fc834bba375e X-Provags-ID: V03:K1:HjK0YiUW2tYMQSMK1fjSnpJewyY+eH7iU2coUBOPcpyJEvcZn3l PtYLQCgIu38WUKKEGvIJCnGt5a7cVDRW73IflfRci3y8DNRtD/OItlYkw/9oD9YNEBhvhdL gOugImfAKdAGHU9C2J9ORiMcBDzReC7pm/cCb8NH+9+vZwyKkdotsaa57VxMjPJQGF1bGLf Hj9Fxa5z5WikOn2VJ3QEQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:7a+Pk/V5n5s=:2HdKLYgQEeTTR7WJGQ+Yvf 67E0P99YcR9Sm6q/nPudAL3i3aSvwC5kVxwIqhPUn6KK7BFowT/MtvFou6kIHr7ImQOjIW921 WYuZCMsauPggrnWX181Bj99vAsl21ZpQq7QVmJKfh1OAaQ5U4y5dKJbEeerhLI0+JaFc7TIZh NkiG7YmLRnIIIy0EnAozcWhcSZGiqCEVd4yL5LQuk+/1ITZCQr/1XjM1Bnze3C/kpHWZAQ03v buQRVdmnluEsSImFhYBaVNxYVYCTJvKmacgW/GBok1nTdNe9PfscQOLQRmmGcWTJDu8Ipunx5 GRcwjY1XZdqO+X7dina7iiF4CAsTSoKvFeOBGadM2eIb2nZ1m32MAr129b8bGCtsmdWCOG1hj 5l1Ixd8O2BlGxleMWCCZBacOLlEaNYz2HYkeTvjhemTPjs8aI2OkizP5oX0gwMfilzC0sN5pD BhIO1F3C2SUB/EvM/YHvue+ub9uJIhfAFd5F9d28uuSR0jH1kgynYefx8P0FhahSpfCTfAJoi 0i2CGyGTfO7XW4ctTvSxzqi6g8mJe8MgNl8dcALkDHTmbkkr0wC6SZPvzmG/gvOSrvtbScBEF M/BT/Mz2BzVNan0+kpzFZiYhkEsOQ58X+3k7c3fsjyNg5UKHue1ENJSWGlUxVVb91+ccwVZeF vUBommbVBdJDwkRcNw28S1fgfIp9GCJJShRIXcIn9wVdDxrTU8b6Fdv9jbNzU0DPktBA= X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.3 required=4.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] Patch series for package per project? X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============1190393146==" Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false --===============1190393146== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="S1BNGpv0yoYahz37" Content-Disposition: inline --S1BNGpv0yoYahz37 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hei hei, it's me again, I want to add some more thoughts on this. O:-) On Thu, Mar 03, 2022 at 09:11:39PM +0100, Alexander Dahl wrote: > Hello Christian, >=20 > On Thu, Mar 03, 2022 at 08:37:45PM +0100, Christian Melki wrote: > > On 3/3/22 18:07, Felix Mellmann wrote: > > > On 03.03.22 15:22, Christian Melki wrote: > > >> Just one barebox version, but for different archs, with different=20 > > >> patchsets. I'd like the patches to live in the same place as they've= =20 > > >> always done, i.e. under patches/package/... > > >> But patches/package/series.$platform or similar does not seem to wor= k? > > >> > > > Would it be an option to put the patches below each of the platformdi= rs? > > >=20 > > > I ran into a similiar situation when starting to migrate to a differe= nt=20 > > > CPU platform. After a couple of years putting serveral "platformconfi= g"=20 > > > files within the same directory as "ptxconfig" I'm now using separate= =20 > > > subdirs for each platform where separate sets of platform dependent= =20 > > > patches are lying. > > >=20 > > > Felix > > >=20 > >=20 > > Hi Felix. > >=20 > > Thanks for the suggestion. > >=20 > > Ideally not. It irks me a bit that patches have to go to a different > > place because they belong to another platform than the "default". Or > > that they have to go somewhere else altogether because they need to be > > split into platforms. > > It doesn't make much sense to me. >=20 > If I understand you correctly, your folder patches/barebox-2022.03.0 > (or whatever common version you use) must look like this somehow, all > patches of the different series interleaved? >=20 > 0001-apples.patch > 0001-foo.patch > 0001-this.patch > 0002-bar.patch > 0002-oranges.patch > 0002-that.patch > 0003-baz.patch > series.one > series.three > series.two Now, what if those series are not mutually exclusive, but certain patches are part of multiple series? Even worse: in different places, like first patch in one, and third patch in the other series? Each call of `git ptx-patches` would change the file numbers in the file names, breaking the other series? > Seriously, that looks messy to me, how should anyone looking at the > directory know which patch belongs to which series without looking at > the series files? What if someone wants to copy/move all patches > belonging to only one series to a different place? What I would do, and in fact I did this with patches for U-Boot for five different boards: throw all patches into one series. Why separate them? Or if that's not possible, put distinct patch series configs/platform-XXX/patches/barebox-2022.03.0 as suggested before. Well, there's one more possibility: put the patch series to different top layers. ;-) Any more possibilities? Happy TIMTOWTDI everyone! ;-) Greets Alex --=20 /"\ ASCII RIBBON | =BBWith the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.=AB / \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie) --S1BNGpv0yoYahz37 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEwo7muQJjlc+Prwj6NK3NAHIhXMYFAmIhJpEACgkQNK3NAHIh XMbaqRAAoXoRi+iAy5sZ3ORTbG63vwSsRN98uCj9iPO1O0fWrJ+bENrFoyUXrEbA aezrm3Lhpe9dBA4/HfFQ/uoQrF83aMA/xMMq1jcNNvgdA14aDskk0xOoI0UH1lfy hemRSTn63Jl4fVNA77Mxz+MfMDe6VsOR/kL8hcspEW/CJA7hp0LC2ZjMbPKFu9pe VTYOryKPdwRiz5NE0BPNc1NEq2LYGF8/jCRVsI7vFlvjt7TAOq4cbT/mPN/92TWm Uvx40l91M0+/HQ6YoSZE4MzkoEHapsC+gjtph+8+vj1q+KWC2gw/MxW9Orxev3c9 OMN5sf4SiI7YOPBuCdDuVvlOjGSY5t1Kvm133PfkE8XGEF3wIPhzf0WGi3fElsKf RIH5/M+P4lvKOz6Q/0YSCU1z56mlMA8zJr4EoHchnFeAeZnc6ahygWknTFXC2vGk 3agYxjkfm4SaLx8/NTXps4c/rplRAEvOImkf5GtkxMHAjVskHMA681sSv2GQdRLq 59DjAffE3DfCsu1x5O31xQ6qQAuITMpV/Ln3JlBe7tecgPVto8xyxijzWwg28LPd N3KrMxwPaiYrhdT+IvIjCQpURUFPBZaAssB2OdDjgK/PLvqY81vZ2ryMhpll8+AK 4a2mNybrR91N8a1ccHe+gTZ00H3Nc9hK1jwJjelguxzUuOkWlNc= =b9cS -----END PGP SIGNATURE----- --S1BNGpv0yoYahz37-- --===============1190393146== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de --===============1190393146==--