http://bugzilla.moblin.org/show_bug.cgi?id=8048
--- Comment #12 from pohly <[email protected]> 2010-03-05 03:16:10 PST --- (In reply to comment #11) > reporting 'per-peer (unshared) properties not allowed: ' is reasonable for a > context when configuring properties. However, it is confusing to me when > printing configs and it seems to me the error won't be triggered since we only > read shared level properties. So you are saying that for "--print-config --source-property sync=none @default" the error should not be printed because the "sync" property is not shown? I think the same argument for not allowing per-peer properties for --configure also applies here, although in a less severe way: the user did something which has no effect, perhaps because he expected it to have an effect, so we should tell him that there is something fishy about his command line. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
