Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S
syncevolution
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 165
    • Issues 165
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SyncEvolution
  • syncevolution
  • Issues
  • #129

Closed
Open
Opened Sep 06, 2010 by Bugzilla Migration User@bugzilla-migration

command line: feedback for --configure

Submitted by Patrick Ohly @pohly

Assigned to SyncEvolution Community

Link to original bug (#52732)

Description

---- Reported by patrick.ohly@intel.com 2010-09-06 12:28:19 +0000 ----

"--configure --source-property evolutionsource/type/...=bar scheduleworld addresssbook"

somewhat unexpectedly modifies the property for all peers in the @default context.

There were several suggestions for avoiding this pitfall. Reject such changes unless a) a -f/--force option is given, or b) there is only one peer in the context or c) the <config> names a context

b) is useful for casual users with only one peer. But they don't learn about the concept of SyncEvolution.

Therefore the proposal in this issue is to add immediate feedback about the changes made to a configuration, for example like this (suggested by Matthijs Kooijman):

Operating on context "default"
Setting property "evolutionsource" to "foo" for source "addressbook"
Setting property "sync" to "two-way" for source "addressbook" and peer "scheduleworld"
Setting property "syncURL" to "http://foo" for peer "scheduleworld"

--- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC ---

This bug was previously known as bug 6351 at https://bugs.meego.com/show_bug.cgi?id=6351

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: SyncEvolution/syncevolution#129