Gnus development mailing list
 help / color / mirror / Atom feed
From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: Problem with agent and empty groups
Date: Wed, 25 Feb 2004 16:59:04 -0500	[thread overview]
Message-ID: <u8zznb695xz.fsf@blackbird.MITRE.ORG> (raw)
In-Reply-To: <u8yisnkn2.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Tue, 24 Feb 2004 18:05:37 -0500")

Well it just happened again.  This time I moved local to local.old and
diff'ed them after local got regenerated by 'g' in the Group buffer.
I suspect the entry with the nil in it is the problem.  I notice than
no entry for that group is created when local is regenerated.

diff -c /home/dsg/.News/agent/nnimap/linus/agent.lib/local.old /home/dsg/.News/agent/nnimap/linus/agent.lib/local
*** /home/dsg/.News/agent/nnimap/linus/agent.lib/local.old	Wed Feb 25 16:56:15 2004
--- /home/dsg/.News/agent/nnimap/linus/agent.lib/local	Wed Feb 25 16:56:15 2004
***************
*** 1,19 ****
- INBOX\.junkmail nil nil
- INBOX\.mitre\.g020\.atm_security 2 2
  INBOX\.mitre\.g020\.sei 19 19
  INBOX\.mitre\.g06a\.rcf-staffing 412 412
- INBOX\.mitre\.collaborative 21 21
  INBOX\.mitre\.g06a\.rcf-vmware 183 183
! INBOX\.mitre\.g06a\.rcf-tasks 525 525
  INBOX\.security\.ids 1 14
! INBOX\.mitre\.java 3 3
  INBOX\.mitre\.g060-MSR-ESCHA 71 71
  INBOX\.mitre\.g06a 48 48
  INBOX\.miscmail 62407 65995
  INBOX\.mitre\.secom\.securid 42 42
- INBOX\.mitre\.g022\.dss 14 14
  INBOX\.mitre\.secom\.wireless 20 258
  INBOX\.solaris 31 31
  INBOX\.mitre\.hr 1 1
  INBOX\.security\.bugtraq 17618 17621
  INBOX\.missedmail 226 226
--- 1,18 ----
  INBOX\.mitre\.g020\.sei 19 19
+ INBOX\.mitre\.g020\.atm_security 2 2
  INBOX\.mitre\.g06a\.rcf-staffing 412 412
  INBOX\.mitre\.g06a\.rcf-vmware 183 183
! INBOX\.mitre\.collaborative 21 21
  INBOX\.security\.ids 1 14
! INBOX\.mitre\.g06a\.rcf-tasks 525 525
  INBOX\.mitre\.g060-MSR-ESCHA 71 71
  INBOX\.mitre\.g06a 48 48
+ INBOX\.mitre\.java 3 3
  INBOX\.miscmail 62407 65995
  INBOX\.mitre\.secom\.securid 42 42
  INBOX\.mitre\.secom\.wireless 20 258
  INBOX\.solaris 31 31
+ INBOX\.mitre\.g022\.dss 14 14
  INBOX\.mitre\.hr 1 1
  INBOX\.security\.bugtraq 17618 17621
  INBOX\.missedmail 226 226
***************
*** 39,54 ****
  INBOX\.security\.firewalls\.fw1 107 107
  INBOX\.mitre\.g060-tides2000 113 113
  CRCF 630 630
- INBOX\.listproc 3 391
  CIIS\.G06A\.Managers 1437 1437
  INBOX\.mitre\.secom\.ids-ops 3592 3592
  INBOX\.emacs\.nnimap 1518 1521
  INBOX\.mitre\.secom 46 46
  INBOX\.mitre\.g06a\.rcf-pki 22 22
  INBOX\.mitre\.g06a\.rcf-tasks-isf 2473 2511
- INBOX\.mitre\.secom\.incidents 1091 1091
- INBOX\.emacs\.misc 141 141
  INBOX\.mitre\.g060-nrrc 49 49
  INBOX\.mitre\.g022 67 67
  INBOX\.mitre\.mdp 119 119
  INBOX\.mitre\.g020 111 111
--- 38,53 ----
  INBOX\.security\.firewalls\.fw1 107 107
  INBOX\.mitre\.g060-tides2000 113 113
  CRCF 630 630
  CIIS\.G06A\.Managers 1437 1437
  INBOX\.mitre\.secom\.ids-ops 3592 3592
+ INBOX\.listproc 3 391
  INBOX\.emacs\.nnimap 1518 1521
  INBOX\.mitre\.secom 46 46
  INBOX\.mitre\.g06a\.rcf-pki 22 22
  INBOX\.mitre\.g06a\.rcf-tasks-isf 2473 2511
  INBOX\.mitre\.g060-nrrc 49 49
+ INBOX\.emacs\.misc 141 141
+ INBOX\.mitre\.secom\.incidents 1091 1091
  INBOX\.mitre\.g022 67 67
  INBOX\.mitre\.mdp 119 119
  INBOX\.mitre\.g020 111 111
***************
*** 57,72 ****
  INBOX\.mitre\.g020\.forensics_tem 6 6
  INBOX\.mitre\.g06a\.rcf-tasks-dodbench 17 17
  INBOX\.mitre\.secom\.multicast 8 8
  INBOX\.infosec 1362 2106
- INBOX\.mitre\.psac 90 90
  INBOX\.security\.sans 589 592
! INBOX\.mitre\.g020\.nccs 37 37
  INBOX\.mitre\.modem_pool 97 97
- INBOX\.emacs\.auctex 2 19
  INBOX\.mitre\.g020\.jefx 51 51
! INBOX\.emacs\.w3 1 42
! INBOX\.mitre\.isis 55 55
  INBOX\.mitre\.osis 42 42
  INBOX\.mitre\.g06a\.rcf-tasks-scif-cluster 83 83
  INBOX\.mitre\.mii 4 4
  INBOX\.mitre\.multicast_moie 217 217
--- 56,71 ----
  INBOX\.mitre\.g020\.forensics_tem 6 6
  INBOX\.mitre\.g06a\.rcf-tasks-dodbench 17 17
  INBOX\.mitre\.secom\.multicast 8 8
+ INBOX\.mitre\.g020\.nccs 37 37
  INBOX\.infosec 1362 2106
  INBOX\.security\.sans 589 592
! INBOX\.mitre\.psac 90 90
  INBOX\.mitre\.modem_pool 97 97
  INBOX\.mitre\.g020\.jefx 51 51
! INBOX\.emacs\.auctex 2 19
  INBOX\.mitre\.osis 42 42
+ INBOX\.mitre\.isis 55 55
+ INBOX\.emacs\.w3 1 42
  INBOX\.mitre\.g06a\.rcf-tasks-scif-cluster 83 83
  INBOX\.mitre\.mii 4 4
  INBOX\.mitre\.multicast_moie 217 217
***************
*** 78,82 ****
  INBOX\.emacs\.efs\.help 1 61
  INBOX\.mitre\.secom\.cve-content-team 577 577
  INBOX\.personal 358 358
- INBOX\.mitre\.unixclass 51 51
  INBOX\.info-afs 6422 7154
--- 77,81 ----
  INBOX\.emacs\.efs\.help 1 61
  INBOX\.mitre\.secom\.cve-content-team 577 577
  INBOX\.personal 358 358
  INBOX\.info-afs 6422 7154
+ INBOX\.mitre\.unixclass 51 51

-- 
Dave Goldberg
david.goldberg6@verizon.net





  reply	other threads:[~2004-02-25 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09 17:20 David S Goldberg
2004-02-09 17:26 ` David S Goldberg
2004-02-09 22:56 ` Kevin Greiner
2004-02-13 21:03   ` David S Goldberg
2004-02-23 17:34     ` David S Goldberg
2004-02-24 23:05       ` Kevin Greiner
2004-02-25 21:59         ` David S Goldberg [this message]
2004-03-04 12:56           ` Kevin Greiner
2004-03-04 15:12             ` Katsumi Yamaoka
2004-03-05 16:28               ` Kevin Greiner
2004-03-06  7:40                 ` Katsumi Yamaoka
2004-03-05 17:02             ` David S Goldberg

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=u8zznb695xz.fsf@blackbird.MITRE.ORG \
    --to=david.goldberg6@verizon.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).