From: "Steven E. Harris" <seh@panix.com>
Subject: Re: (Yet another stab at) Sharing ~/.newsrc.eld among multiple
Date: Thu, 06 Nov 2003 17:22:39 -0800 [thread overview]
Message-ID: <q67sml1km5c.fsf@panix.com> (raw)
In-Reply-To: <uk76dm6zl.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Thu, 06 Nov 2003 17:07:10 -0600")
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> I'd appreciate your feedback.
>
> You'll need the latest versions from CVS before applying the diffs.
I got the CVS head and applied your patch. All built well and I see
after my first run that gnus-agent-covered-methods is gone from
~/.newsrc.eld. Was that intentional? The server definitions aren't
just shortened; they're not even present. The agent seems to behave
well and remembers which groups are agentized. Cool.
Now that I'm riding this CVS bandwagon, what is the best tactic to
incorporate updates. Do you do a "configure/make/make install" after
each "cvs update"? Or do you just run the Gnus code right out of the
CVS checkout directory? I guess the latter would just forgo the "make
install" step. Is that correct?
--
Steven E. Harris :: seh@panix.com
next prev parent reply other threads:[~2003-11-07 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 20:03 (Yet another stab at) Sharing ~/.newsrc.eld among multiple machines Steven E. Harris
2003-11-06 22:24 ` (Yet another stab at) Sharing ~/.newsrc.eld among multiple Simon Josefsson
2003-11-06 22:43 ` Steven E. Harris
2003-11-06 23:49 ` Simon Josefsson
2003-11-06 23:07 ` Kevin Greiner
2003-11-07 1:22 ` Steven E. Harris [this message]
2003-11-07 3:22 ` Kevin Greiner
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=q67sml1km5c.fsf@panix.com \
--to=seh@panix.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 NNTP newsgroup(s).