Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: Rod Whitby <list.ding@rwhitby.net>
Subject: Re: expiry-target
Date: 13 Aug 2000 18:16:57 -0700	[thread overview]
Message-ID: <m2aeegej5i.fsf@ognus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: Rod Whitby's message of "14 Aug 2000 08:59:49 +0930"

Rod Whitby <list.ding@rwhitby.net> writes:

> Harry Putnam <reader@newsguy.com> writes:
> > I only have nnml groups but haven't been able to get this working.
> > 
> > Can you supply an example of the necessary var settings and the code
> > that would be appropriate in group params.  Maybe even replete with
> > some of the good Lars humor.

[...]

> 
> And I've twice now supplied the patches which makes it work.  Are my
> messages getting through to the list, or are they going into a black
> hole somewhere ?  Harry or Lars, can you please reply to me personally
> if you see this message on the list.  I've CC'd Lars just in case
> there is something which is stopping my messages getting to the list.
 
[...]

Rob,
Sorry to have steadfastly ignored your patches.  My reasons were, that
I have very little experience using patches, the few times I have it
has been directly from a gnus article buffer to the appropriate el
files, via the `O p' command (save to a pipe) piping to patch.

In this case patch tells me it sees only garbage in the patch.
Probably something I'm doing wrong.

Secondly in your several posts on this, including patches, you have
steadfastly refused to supply an example of how this works or what it
looks like.  Being a lisp illiterate, I need to see examples to see
how it is supposed to work.

So on the strenghth of your most recent post.  I saved your patch to
file (expiry-patch.diff)  put it in pgnus/lisp and called 
`patch <expiry-patch.diff'  The patch went in smoothly and reported:

   /usr/local/pgnus/lisp $ patch <expiry-patch.diff
   patching file `gnus-sum.el'
   Hunk #1 succeeded at 7683 (offset 1 line).
   patching file `nnml.el'
   patching file `nnmail.el'

Now what?






  reply	other threads:[~2000-08-14  1:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-16  2:12 expiry-target Harry Putnam
2000-08-13 18:52 ` expiry-target Lars Magne Ingebrigtsen
2000-08-13 19:10   ` expiry-target Harry Putnam
2000-08-13 23:29     ` expiry-target Rod Whitby
2000-08-14  1:16       ` Harry Putnam [this message]
2000-08-14  3:17         ` expiry-target Rod Whitby
2000-08-14  4:14           ` expiry-target Harry Putnam
2000-08-14  4:23             ` expiry-target Rod Whitby
2000-08-14 12:15               ` expiry-target Harry Putnam
2000-08-14 22:49                 ` expiry-target Rod Whitby
2000-08-14 23:06                   ` expiry-target Harry Putnam
2000-08-14  8:15           ` expiry-target Kai Großjohann
2000-08-14  8:11       ` expiry-target Kai Großjohann
2000-08-14  8:14         ` expiry-target Rod Whitby
2000-08-14  8:12       ` expiry-target Kai Großjohann
2000-08-14 17:13       ` expiry-target Lars Magne Ingebrigtsen
2000-08-14 22:36         ` expiry-target Harry Putnam
2000-08-14 23:08           ` expiry-target Harry Putnam
2000-08-13 19:35   ` expiry-target Kai Großjohann
2002-09-27 11:33 expiry-target Mike Woolley

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=m2aeegej5i.fsf@ognus-5.8.8-cvs.now.playing \
    --to=reader@newsguy.com \
    --cc=list.ding@rwhitby.net \
    /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).