From: Dan Christensen <jdc@julian.uwo.ca>
Subject: Re: where to get gpg.el
Date: 16 Nov 2000 01:24:39 -0500 [thread overview]
Message-ID: <87g0ksfn88.fsf@scratchy.dhis.org> (raw)
In-Reply-To: <2nd7fwh9gc.fsf@tiger.jia.vnet>
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Dan Christensen <jdc@julian.uwo.ca> writes:
>
> > I just upgraded gnus from cvs and several files disappeared: gpg.el,
> > gpg-ring.el, base64.el and md5.el. Now verifying of signed messages
> > isn't working. Were these removed on purpose (e.g. waiting for
> > copyright assignments)? If so, can I get them from somewhere?
> > Or is this because the development version isn't on the main branch?
> > If so, how do I get the development version via cvs?
>
> They are in the contrib directory.
I don't have a contrib directory. How do I get it? [Sorry if this is
obvious to people who are cvs experts, but presumably there are others
in my boat too.]
Dan
next prev parent reply other threads:[~2000-11-16 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 16:07 MML Security docs Simon Josefsson
2000-11-16 3:07 ` where to get gpg.el Dan Christensen
2000-11-16 3:39 ` ShengHuo ZHU
2000-11-16 6:24 ` Dan Christensen [this message]
2000-11-16 7:08 ` Kevin Falcone
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=87g0ksfn88.fsf@scratchy.dhis.org \
--to=jdc@julian.uwo.ca \
/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 NNTP newsgroup(s).