From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Using a Gnus for collaborative work & todo list mgmt?
Date: 29 May 1996 23:13:48 +0200 [thread overview]
Message-ID: <x67mtvb2sz.fsf@eyesore.no> (raw)
In-Reply-To: Kai Grossjohann's message of 29 May 1996 11:28:18 +0200
Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:
> Now the main issue: what kind of backend could we use that
> - allows read/write access
> - doesn't cause too many problems with several people writing (I'm
> not even concerned about locking, it's just that I'm unsure about
> .overview files, for example -- what happens if somebody adds
> something to the .overview file while I'm reading a group -- will
> the new article just appear the next time I get new news?)
For that reason alone I would suggest using nnmh -- one file per
article, no active file, no .overview file to cause problems.
I was thinking along similar lines a few weeks back for the gnus-bug
group. I think server-side annotations could be used. For instance,
all new messages to gnus-bug won't have any annotations. Then I could
ask the nnml server for all articles in that group without any
annotations. As I process the bug reports, I could add annotations
like "fixed", "queried for more information", "not a bug", etc.
Of course, we don't have annotations at all in Gnus yet, but I'll
definitely be adding them for Red Gnus.
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-05-29 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-29 9:28 Kai Grossjohann
1996-05-29 21:13 ` Lars Magne Ingebrigtsen [this message]
1996-05-30 15:05 ` Kai Grossjohann
1996-05-31 1:22 ` Lars Magne Ingebrigtsen
1996-05-31 14:05 ` Kai Grossjohann
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=x67mtvb2sz.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).