From: Tom Tromey <tromey@redhat.com>
To: Casey Marshall <csm@gnu.org>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: X.509 certificate tests
Date: Tue, 26 Oct 2004 17:20:00 -0000 [thread overview]
Message-ID: <m3r7nlfldm.fsf@localhost.localdomain> (raw)
In-Reply-To: <87mzy9h0ea.fsf@gnu.org>
Casey> The only really problematic part are the certificate data: they are
Casey> about 2.6M of binary goo. Any problem with including them?
As long as there are no legal issues I don't see a problem. My copy
of mauve seems to be about 14M already, a few more megabytes won't
hurt.
Tom
next prev parent reply other threads:[~2004-10-26 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 5:46 Casey Marshall
2004-10-26 15:46 ` Tom Tromey
2004-10-26 17:09 ` Casey Marshall
2004-10-26 17:20 ` Tom Tromey [this message]
2004-10-26 17:58 ` Casey Marshall
2004-10-26 20:33 ` Mark Wielaard
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=m3r7nlfldm.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=csm@gnu.org \
--cc=mauve-discuss@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).