Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Problems with gnus-registry
Date: Thu, 07 Feb 2008 10:42:10 -0500	[thread overview]
Message-ID: <76bq6sai3x.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <8663x2at4h.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 06 Feb 2008 11:31:58 -0600")

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

   TZ> Gnus v5.10.8 is not up to date with all my changes lately.  I'd
   TZ> suggest using a CVS checkout if possible; you can try updating just
   TZ> gnus-registry.el but it may break badly as the registry gets
   TZ> integrated more into Gnus as a whole.

I will look into this.  Right now it looks like my unix box cannot connect
to cvs.gnus.org.  :-(

Are the nightly builds reasonably safe to check out?  It does not look like
this is any official build that is newer than v5.10.8, is there?


I am looking into using match by subject since that it is one header that
should always be there.  Ufortunately, the message included below (I am
showing all available headers) did not get registered and filed correctly
even though I think it should have matched by subject.  (BTW I am pretty
sure that the embedded space in the subject is not the issue).

==========================================================

  Received: by hamilton.ppllc.com 
  	  id <01C868E5.2C6CB3A0@hamilton.ppllc.com>; Wed, 6 Feb 2008 12:24:48 -0500
  Message-ID: <0B72769B5EA61E45BFDAB9B849923FE703359AC5@hamilton.ppllc.com>
  From: Andrew Vickers <vickers@ppllc.com>
  To: Jacob Colman <colman@ppllc.com>
  Cc: Chirag Patel <patel@ppllc.com>
  Subject: RE: PM-331 Asset Position Updates into VM FS - ready for tech rev  iew
  Date: Wed, 6 Feb 2008 12:24:39 -0500 
  MIME-Version: 1.0
  Content-Type: text/plain

==========================================================

Looking into the registry, the message is registered correctly.  But if I
execute (message-fetch-field "subject") on this message, I get the following:

"RE: PM-331 Asset Position Updates into VM FS - ready for tech rev  iew, Re: PM-331 Asset Position Updates into VM FS - ready for tech"

This looks like it duplicates the text in the subject header which, of
course, will not match that which is registered.

Is this a bug in the v5.10.8 version of the registry?

...Jake

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com



  reply	other threads:[~2008-02-07 15:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:21 Jake Colman
2008-02-01 20:57 ` Ted Zlatanov
2008-02-04 13:38   ` Jake Colman
2008-02-04 21:03     ` Ted Zlatanov
     [not found]       ` <76y7a0nyo3.fsf@dev-d01.ppllc.com>
     [not found]         ` <86lk60uwwq.fsf@lifelogs.com>
     [not found]           ` <764pconmz4.fsf@dev-d01.ppllc.com>
2008-02-05 15:15             ` Ted Zlatanov
2008-02-05 21:51               ` Jake Colman
2008-02-05 22:15                 ` Ted Zlatanov
2008-02-05 22:24                   ` Jake Colman
2008-02-06 14:21                     ` Ted Zlatanov
2008-02-06 16:54                       ` Jake Colman
2008-02-06 17:31                         ` Ted Zlatanov
2008-02-07 15:42                           ` Jake Colman [this message]
2008-02-06 20:05                       ` Reiner Steib
2008-02-07 15:43                         ` Ted Zlatanov
2008-02-07 17:29                           ` Reiner Steib
2008-02-08 11:58                             ` David
2008-02-14 17:51                               ` Ted Zlatanov
2008-02-28 15:01                                 ` Ted Zlatanov
2008-02-28 15:53                                   ` David
2008-02-14 17:45                             ` Ted Zlatanov
2008-02-28 15:03                               ` Ted Zlatanov

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=76bq6sai3x.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.com \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.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).