anchor.diff:  #
   # {sync_channel_name} must exist in the section of SYNC_CHANNELS:
   #
  -# NOTE:
  -# Articles between past 90 days and future 90 days in MHC will be
  -# published to the target Google Calendar.  90 is hard-coded in
  -# lib/mhc/calendar.rb for now. Other articles out of the range in
  -# Google Calendar will be DELETED.
  -#
   # Before the first try, I recommend you to make a new calendar on your
   # Google Calendar dedicated to MHC.  and backup your local spool of
   # MHC.
  
positive.code: ## Google Calendar
  
  # Currently, Google Calendar stuffs work only as destinations
  # to publish from local MHC calendars.
  #
  # Since MHC uses standard CalDAV protocol, I believe
  # it works with other CalDAV-based network calendars such as
  
negative.code: ################################################################
  
  # Each sync channel binds two CALENDARS (see below) for
  # data-synchronization.  Currently, STRATEGY allows:
  #
  # + "mirror" :: mirrors CALENDAR1 to CALENDAR2.
  #               CALENDAR1 must be a local MHC calendar,
  #               and CALENDAR2 must be a Google Calendar.
  #               Note that articles between past 90 days and future 90
  #               days in MHC will be mirrored to the target Google
  #               Calendar.  90 is hard-coded in lib/mhc/calendar.rb for
  #               now. Other articles out of the range in Google
  #               Calendar will be DELETED.
  # + "import" :: imports newly created (non-recurring) articles
  #               on CALENDAR1 into CALENDAR2.
  #               CALENDAR1 must be a Google Calendar,
  #               and CALENDAR2 must be a local MHC calendar.
  #               All articles in CALENDAR1 will be DELETED after
  #               the import.
  #
  # True two-way sync is not yet implemented.
  
  - NAME: business
    CALENDAR1: business
  