From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Alexander Dahl <ada@thorsis.com>, Ladislav Michl <ladis@linux-mips.org>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC 3/4] libptxdist: add a function to find unreferenced source directories
Date: Mon, 9 Sep 2019 08:23:00 +0200 [thread overview]
Message-ID: <20190909062300.w6jbjiywrl5oqrva@pengutronix.de> (raw)
In-Reply-To: <4933953.zd8LfGRCK0@ada>
On Wed, Sep 04, 2019 at 03:16:51PM +0200, Alexander Dahl wrote:
> Am Mittwoch, 4. September 2019, 15:05:04 CEST schrieb Michael Olbrich:
> > On Fri, Aug 23, 2019 at 11:01:58AM +0200, Alexander Dahl wrote:
> > > FWIW, we are still using different versions of at91bootstrap in different
> > > BSPs. The legacy version (at91bootstrap) has patches in the directory
> > > 'patches/Bootstrap-v1.16' and the current version (at91bootstrap2) has
> > > them in 'patches/at91bootstrap-3.8.13'.
> > >
> > > If one or the other package needs fixes, let me know.
> >
> > PTXdist upstream has patches for 'at91bootstrap'. Do you use those, or do
> > you have your own patch stack in your BSP?
> >
> > I'd like to remove the patches from PTXdist. It's the only packages that
> > has a configurable version and patches for one specific version upstream.
>
> We have our own patches anyway.
>
> And even if not, it would also be no problem to add them to our BSP, if
> ptxdist won't ship those anymore.
Hmm, so I noticed that I actually run build tests for this. And I'd
probably loose those if I drop the patches...
So another Idea: From what I understand, Upstream for this is dead, so
there will be no new version, right? Can I assume, that nowadays only
version 1.16 is used?
In that case I could just remove the version options and keep the patches.
That way all my scripts are happy and it's still covered in my build tests.
Alex, would that make sense to you?
Ladis, you submitted the last patch for this. Is this still relevant for
you? What do you think?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-09 6:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 10:42 [ptxdist] [RFC 1/4] patches/HEADER: remove apparently outdated and unreferenced file Roland Hieber
2019-08-22 10:42 ` [ptxdist] [RFC 2/4] Makefile.in: sort environment tools alphabetically Roland Hieber
2019-08-22 10:42 ` [ptxdist] [RFC 3/4] libptxdist: add a function to find unreferenced source directories Roland Hieber
2019-08-22 10:53 ` Roland Hieber
2019-08-22 12:43 ` Uwe Kleine-König
2019-08-22 15:38 ` Michael Olbrich
2019-08-23 8:33 ` Roland Hieber
2019-08-23 9:01 ` Alexander Dahl
2019-09-04 13:05 ` Michael Olbrich
2019-09-04 13:16 ` Alexander Dahl
2019-09-09 6:23 ` Michael Olbrich [this message]
2019-09-09 7:46 ` Alexander Dahl
2019-09-09 20:33 ` Ladislav Michl
2019-09-10 8:13 ` Michael Olbrich
2019-08-22 10:42 ` [ptxdist] [RFC 4/4] ptxdist: add a 'lint' subcommand Roland Hieber
2019-08-22 11:44 ` [ptxdist] [RFC 1/4] patches/HEADER: remove apparently outdated and unreferenced file Robert Schwebel
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=20190909062300.w6jbjiywrl5oqrva@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ada@thorsis.com \
--cc=ladis@linux-mips.org \
--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