From: Alexander Dahl <post@lespocky.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Patch series for package per project?
Date: Thu, 3 Mar 2022 21:11:39 +0100 [thread overview]
Message-ID: <20220303201138.GB26895@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <00ae8995-135e-dc67-737e-4c7d6ec3e08a@t2data.com>
[-- Attachment #1.1: Type: text/plain, Size: 2152 bytes --]
Hello Christian,
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
> >> patchsets. I'd like the patches to live in the same place as they've
> >> always done, i.e. under patches/package/...
> >> But patches/package/series.$platform or similar does not seem to work?
> >>
> > Would it be an option to put the patches below each of the platformdirs?
> >
> > I ran into a similiar situation when starting to migrate to a different
> > CPU platform. After a couple of years putting serveral "platformconfig"
> > files within the same directory as "ptxconfig" I'm now using separate
> > subdirs for each platform where separate sets of platform dependent
> > patches are lying.
> >
> > Felix
> >
>
> Hi Felix.
>
> Thanks for the suggestion.
>
> 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.
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?
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
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?
Puzzled greetings
Alex
--
/"\ ASCII RIBBON | »With 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.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-03-03 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 9:17 Christian Melki
2022-03-03 13:40 ` Michael Olbrich
2022-03-03 14:22 ` Christian Melki
2022-03-03 17:07 ` Felix Mellmann
2022-03-03 19:37 ` Christian Melki
2022-03-03 20:11 ` Alexander Dahl [this message]
2022-03-03 20:35 ` Alexander Dahl
2022-03-04 8:10 ` Michael Olbrich
2022-03-04 8:24 ` Christian Melki
2022-03-04 15:16 ` Christian Melki
2022-03-04 15:34 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220303201138.GB26895@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox