Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup errors with 0 messages in a folder
Date: Tue, 24 Jul 2007 10:52:56 -0700	[thread overview]
Message-ID: <1185299474-sup-18@south> (raw)
In-Reply-To: <20070723210334.GA19236@electricrain.com>

A non-text attachment was scrubbed...
Name: a.patch
Type: application/octet-stream
Size: 446 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070724/711d24a5/attachment-0001.obj 


  reply	other threads:[~2007-07-24 17:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 21:03 Dan Sully
2007-07-24 17:52 ` William Morgan [this message]
2007-07-24 18:14   ` Dan Sully
2007-07-24 18:26     ` Dan Sully
2007-07-24 22:14       ` William Morgan
2007-07-24 22:22         ` Dan Sully
2007-07-25  0:00           ` William Morgan

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=1185299474-sup-18@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