On 04-Oct-18 11:46 AM, Ferruh Yigit wrote:
On 10/4/2018 10:18 AM, Thomas Monjalon wrote:
04/10/2018 11:17, Burakov, Anatoly:
On 03-Oct-18 11:05 PM, Thomas Monjalon wrote:
20/09/2018 17:41, Anatoly Burakov:
Currently, command-line switches for legacy mem mode or single-file
segments mode are o
On 10/4/2018 10:18 AM, Thomas Monjalon wrote:
> 04/10/2018 11:17, Burakov, Anatoly:
>> On 03-Oct-18 11:05 PM, Thomas Monjalon wrote:
>>> 20/09/2018 17:41, Anatoly Burakov:
Currently, command-line switches for legacy mem mode or single-file
segments mode are only stored in internal config.
04/10/2018 11:17, Burakov, Anatoly:
> On 03-Oct-18 11:05 PM, Thomas Monjalon wrote:
> > 20/09/2018 17:41, Anatoly Burakov:
> >> Currently, command-line switches for legacy mem mode or single-file
> >> segments mode are only stored in internal config. This leads to a
> >> situation where these flags
On 03-Oct-18 11:05 PM, Thomas Monjalon wrote:
20/09/2018 17:41, Anatoly Burakov:
Currently, command-line switches for legacy mem mode or single-file
segments mode are only stored in internal config. This leads to a
situation where these flags have to always match between primary
and secondary, w
20/09/2018 17:41, Anatoly Burakov:
> Currently, command-line switches for legacy mem mode or single-file
> segments mode are only stored in internal config. This leads to a
> situation where these flags have to always match between primary
> and secondary, which is bad for usability.
>
> Fix this
Currently, command-line switches for legacy mem mode or single-file
segments mode are only stored in internal config. This leads to a
situation where these flags have to always match between primary
and secondary, which is bad for usability.
Fix this by storing these flags in the shared config as
6 matches
Mail list logo