Feature request: mark client config options to be placed under Custom Options without being analyzed in the import process

[GoogleCodeExporter]

It would be great to have the possibility of somehow marking the config options 
in the client config file prior to importing it, so that all options that are 
say prefixed with a special character (say & or %) will not be analyzed by the 
importing process, but instead placed as is under Custom Options.
Thanks!

Original issue reported on code.google.com by a.anisch...@dekart.com on 7 Nov 2014 at 4:53

• Merged into: #2

[GoogleCodeExporter]

Normally this should not be needed. I know that this is currently needed for 
multiple remotes but I am planning multiple servers for one of the next 
releases. All other unrecognized options should be put under custom options.

Original comment by arne@rfc2549.org on 7 Nov 2014 at 5:42

• Changed state: Invalid

[GoogleCodeExporter]

Normally this should not be needed. I know that this is currently needed for 
multiple remotes but I am planning multiple servers for one of the next 
releases. All other unrecognized options should be put under custom options.

Original comment by arne@rfc2549.org on 7 Nov 2014 at 5:42

[GoogleCodeExporter]

Original comment by arne@rfc2549.org on 7 Nov 2014 at 5:43

• Changed state: Duplicate