From: Jan Engelhardt <jengelh@inai.de>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] build: restore -version-info
Date: Sun, 1 Jul 2012 18:03:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.01.1207011754110.17716@frira.zrqbmnf.qr> (raw)
In-Reply-To: <alpine.DEB.2.00.1207011409470.2289@blackhole.kfki.hu>
On Sunday 2012-07-01 14:11, Jozsef Kadlecsik wrote:
>> >>
>> >> Correct -- if you had stayed with "-version-info", which you did not.
>> >
>> >So if it's reverted back (second part of your patch), the the first part
>> >is to be skipped.
>>
>> Since you already have made a release (ipset-6.13) emitting an .so.3
>> file, I don't think you should go back to .so.2. Hence I am using 3:0:0.
>
>What I meant is to keep LIBVERSION = 3:0:1, because that's right from
>backward compatibility view, and restore back -version-info.
What part was unclear?
* 6.13 uses -version-number 3:0:1
* that causes production of .so.3
* it's set in stone
* next incompatible change requires use of .so.4
* going back to .so.2 not a good idea
* humans are prone to errors and
would reuse .so.3 in error
* therefore the patch makes a clean restart,
using -version-info 3:0:0, to continue using .so.3
starting from ipset-6.13 until the next *real*
incompatible change.
(If you care about the uninteresting third digit,
-version-info 3:1:0 would be wanted.)
next prev parent reply other threads:[~2012-07-01 16:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 20:04 [ANNOUNCE] ipset 6.13 released Jozsef Kadlecsik
2012-06-30 18:47 ` Jan Engelhardt
2012-06-30 18:47 ` [PATCH] build: restore -version-info Jan Engelhardt
2012-06-30 22:05 ` Jozsef Kadlecsik
2012-06-30 22:15 ` Jan Engelhardt
2012-06-30 22:31 ` Jozsef Kadlecsik
2012-06-30 22:50 ` Jan Engelhardt
2012-07-01 12:11 ` Jozsef Kadlecsik
2012-07-01 16:03 ` Jan Engelhardt [this message]
2012-07-01 17:20 ` Jozsef Kadlecsik
2012-07-01 18:36 ` Jan Engelhardt
2012-07-01 20:45 ` Jozsef Kadlecsik
2012-07-01 10:46 ` [ANNOUNCE] ipset 6.13 released Mr Dash Four
2012-07-01 12:09 ` Jozsef Kadlecsik
2012-07-01 12:19 ` Mr Dash Four
2012-07-01 12:37 ` Jozsef Kadlecsik
2012-07-01 12:44 ` Mr Dash Four
2012-07-01 12:52 ` Jozsef Kadlecsik
2012-07-01 13:17 ` Mr Dash Four
2012-07-01 15:21 ` Jozsef Kadlecsik
2012-07-01 16:52 ` Mr Dash Four
2012-07-01 21:30 ` Neal Murphy
2012-07-01 21:55 ` Jan Engelhardt
2012-07-01 22:59 ` Neal Murphy
2012-07-01 22:58 ` Amos Jeffries
2012-07-01 22:58 ` Amos Jeffries
2012-07-02 7:54 ` Jozsef Kadlecsik
2012-07-02 13:11 ` Mr Dash Four
2012-07-02 13:26 ` Jozsef Kadlecsik
2012-07-02 14:28 ` Mr Dash Four
2012-07-02 20:26 ` Jozsef Kadlecsik
2012-07-10 16:27 ` Alex Bligh
2012-07-10 16:27 ` Alex Bligh
2012-07-01 18:32 ` Steven Kath
2012-07-01 13:21 ` Andreas Herz
2012-07-01 14:44 ` Jozsef Kadlecsik
2012-07-10 9:12 ` Andreas Herz
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=alpine.LNX.2.01.1207011754110.17716@frira.zrqbmnf.qr \
--to=jengelh@inai.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.