Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] unable to sup-sync (new install)
Date: Mon, 17 Sep 2007 11:59:40 -0700	[thread overview]
Message-ID: <1190055410-sup-4972@south> (raw)
In-Reply-To: <20070917180710.GI27677@horacrux>

Excerpts from Kevin Mark's message of Mon Sep 17 11:07:10 -0700 2007:
> Here is a sample:
> /home/kevin/Maildir/.people.cothrige
> /home/kevin/Maildir/.people.cothrige/cur
> /home/kevin/Maildir/.people.cothrige/new
> /home/kevin/Maildir/.people.cothrige/tmp
> /home/kevin/Maildir/.people.enrico_zini

Ah, maildir folders. I will have to write some code to support this.
Sorry!

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2007-09-17 18:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17  3:26 Kevin Mark
2007-09-17 17:12 ` William Morgan
2007-09-17 18:07   ` Kevin Mark
2007-09-17 18:59     ` William Morgan [this message]
2007-09-18  6:26       ` Kevin Mark
2007-09-18  6:27     ` Magnus Therning
2007-09-18 23:18       ` William Morgan
2007-09-19  1:39         ` Kevin Mark
2007-09-18  6:38   ` Magnus Therning
2007-09-18  6:54     ` Kevin Mark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1190055410-sup-4972@south \
    --to=wmorgan-sup@masanjin.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox