All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] RE: emails
Date: Mon, 12 Mar 2001 17:24:33 -0600	[thread overview]
Message-ID: <20010312172433.G31067@sistina.com> (raw)
In-Reply-To: <200103122302.f2CN2GL00700@webber.adilger.int>; from adilger@turbolinux.com on Mon, Mar 12, 2001 at 04:02:16PM -0700

[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]

On Mon, Mar 12, 2001 at 04:02:16PM -0700, Andreas Dilger wrote:
> I don't have problems with AJ's emails (or any other PGP signed messages
> for that matter), even though I currently don't actually do PGP myself.
> However, the post in question just appeared as empty in my mailer (elm).
> The entire body was in an attachment "smime.p7m" which I had to save to
> disk to look at.  For that matter, it was poorly sent (IMHO) twice as
> an uncompressed 25k line email.  Luckily I have a fast net connection.
> I'm also not about to get a new email program...

Ah...my bad...forgot about that one.  Sorry for going off.  Yeah, that's
odd.  It basically appeared as a one-liner for me in mutt.  I could open it
from mutt, but yeah, it was odd.  This is the first time I've seen this
though...stupid M$ LookOUT!

> Maybe we should put a size cap on emails sent to linux-lvm?  This will
> encourage people to use bugzilla.  Also, most of the large patches go to
> lvm-devel (mine at least).  If possible, the "rejection" email for large
> emails should mention the bugzilla web page URL for convenience.

That might make sense.  Can we assume everyone has access to a browser and
will be willing to use if for bug reports?  I know it makes it a lot easier
for us as developers to track the bugs if they are reported there, but I'm
not sure that everyone is willing to do so.   Plus, many times people send
bug reports from the console during the LVM install process, and so may not
have easy access to a browser.  I know Heinz initially had some concern about
limiting file size on the list, so we'll have to get his opinion on this.

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-379-3951
1313 5th St SE, Suite 111              Fax:    612-379-3952
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
I have yet to meet a C compiler that is more friendly and easier to use
than eating soup with a knife.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-03-12 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-12 21:53 [linux-lvm] RE: emails Jones, Steven
2001-03-12 22:15 ` AJ Lewis
2001-03-12 22:27 ` Eric M. Hopper
2001-03-12 23:02   ` Andreas Dilger
2001-03-12 23:24     ` AJ Lewis [this message]
2001-03-13  1:35       ` Heinz J. Mauelshagen
2001-03-13 21:16       ` Ralph Jennings

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=20010312172433.G31067@sistina.com \
    --to=lewis@sistina.com \
    --cc=linux-lvm@sistina.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.