From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Re: On the road to 4.2
Date: Mon, 28 Mar 2005 22:48:00 -0000 [thread overview]
Message-ID: <20050328190453.GB14769@wookimus.net> (raw)
In-Reply-To: <20050328162740.GC31057@wookimus.net>
[-- Attachment #1.1: Type: text/plain, Size: 1122 bytes --]
For those interested in the GNU Arch revision control software, I've
been playing around with cscvs [1]_, a Python cvs-to-tla gateway
application. I imported the entire cvs trunk into GNU Arch, but ran
into a problem with signed v.s. unsigned archives. With 918 changesets,
I didn't want to have to type in my gpg passphrase each time. So, I've
also been playing around with gpg-agent, found in the gnupg development
branch. I'm happy to say it works well with even the older 1.2.x series
of gpg clients with the "use-agent" command-line switch or config file
option. Note, you also need a pinentry agent installed to collect the
PIN or passphrase. I haven't gotten the pinentry-curses app to work
yet, but pinentry-gtk-2 works beautifully, even over an ssh-tunnel via
cable-modem.
So, I'll be signing my copy of the cvs trunk archive and mirroring it to
my personal website later this week (tonight maybe). I'll update you on
the location when it gets mirrored.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2005-03-28 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:17 Chad Walstrom
2005-03-28 22:48 ` Chad Walstrom [this message]
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=20050328190453.GB14769@wookimus.net \
--to=chewie@wookimus.net \
--cc=help-gnats@gnu.org \
/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).