Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] maildir: Allow ', ' in the unique-name portion of a maildir filename.
Date: Tue, 18 Aug 2009 10:33:33 -0700	[thread overview]
Message-ID: <1250616640-sup-2613@masanjin.net> (raw)
In-Reply-To: <20090815042943.GA2414@yoom.home.cworth.org>

Reformatted excerpts from Carl Worth's message of 2009-08-14:
> A unique name can be anything that doesn't contain a colon (or slash)
> and doesn't start with a dot.

I've applied this patch directly to master. (The one I complained about
was attached to your original email; I just noticed this one was
different now.)

> Argh! What's worse than Forgotten Attachment Syndrome (FAS),
> (especially on my first post to a list)?

Since Sup should now work for you, you'll be happy to know that it warns
you if you use the word "attachment" without attaching anything. :)
-- 
William <wmorgan-sup at masanjin.net>


       reply	other threads:[~2009-08-18 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090815042943.GA2414@yoom.home.cworth.org>
2009-08-18 17:33 ` William Morgan [this message]
2009-08-18 17:49   ` Carl Worth
2009-08-18 17:54     ` 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=1250616640-sup-2613@masanjin.net \
    --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