From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libfuse: fix internal version number
Date: Sun, 28 Feb 2016 20:40:28 +0100 [thread overview]
Message-ID: <87povgpqs3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <DE460A1C536D48268A62487407ABE68C@ROLANDAMD64> (Roland Franke's message of "Sun, 28 Feb 2016 20:22:03 +0100")
>>>>> "Roland" == Roland Franke <fli4l@franke-prem.de> writes:
Hi,
>> What is the practical impact of this? Is it purely cosmetical?
> In the system (fli4l) we have fix filenames inside the system.
> So how can we differ without correct filenames?
> How should we know if there is the real version 2.9.4 or the version
> 2.9.5 will be used?
> How should be known if changes between version 2.9.4 and 2.9.5
> realy be installed?
> So the result is more cosmetical for most users. But in situations you
> have more versions available for download, you should be sure to have
> an right version-number.
Ok, so in the context of Buildroot itself, it is purely
cosmetical. Thanks.
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2016-02-28 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 14:05 [Buildroot] [PATCH 1/1] package/libfuse: fix internal version number Bernd Kuhls
2016-02-28 15:54 ` Arnout Vandecappelle
2016-02-28 16:04 ` Roland Franke
2016-02-28 17:47 ` Peter Korsgaard
2016-02-28 19:22 ` Roland Franke
2016-02-28 19:40 ` Peter Korsgaard [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=87povgpqs3.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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