mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libmodbus: adapt help text to the reality
Date: Sat, 11 Mar 2023 22:48:19 +0100	[thread overview]
Message-ID: <ZAz3I+XF7LLMC5xC@lenoch> (raw)
In-Reply-To: <9cdd6b6076b14c6b97286fad7de99f9c4325468f.camel@pengutronix.de>

On Fri, Mar 10, 2023 at 01:49:28PM +0100, Juergen Borleis wrote:
> Am Freitag, dem 10.03.2023 um 12:57 +0100 schrieb Michael Olbrich:
> > On Thu, Mar 09, 2023 at 02:29:25PM +0100, Juergen Borleis wrote:
> > > It is even more worse: 2.x.x API != 3.0.x API != 3.1.x API 🙂
> > 
> > I'm tempted to say we just need 3.1.x in PTXdist upstream. Unless updating
> > an application from 3.0.x to 3.1.x is difficult, because the API changed
> > a lot?
> 
> I don't know. I read the documentation and it just pointed out this API
> incompatibility. Thus, no idea how difficult it would be to port a user from
> 3.0.x to 3.1.x.

There are no in-tree libmodbus users, so let's put it simple: any out of
tree package depending on 3.0.x will carry local libmodbus 3.0.x rule
or update to 3.1.x ;-)

	ladis



      reply	other threads:[~2023-03-11 21:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  9:08 Juergen Borleis
2023-03-09  9:29 ` Michael Olbrich
2023-03-09  9:38   ` Alexander Dahl
2023-03-09 13:24     ` Ladislav Michl
2023-03-09 13:29       ` Juergen Borleis
2023-03-10 11:57         ` Michael Olbrich
2023-03-10 12:49           ` Juergen Borleis
2023-03-11 21:48             ` Ladislav Michl [this message]

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=ZAz3I+XF7LLMC5xC@lenoch \
    --to=oss-lists@triops.cz \
    --cc=jbe@pengutronix.de \
    --cc=m.olbrich@pengutronix.de \
    --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