Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
Subject: Re: GNATS backend?
Date: Fri, 25 Jan 2002 08:20:55 -0800	[thread overview]
Message-ID: <sdsn8ucsgo.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <m33d12t4ro.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 19 Jan 2002 22:22:35 +0100")

>>>>> On Sat, 19 Jan 2002 22:22:35 +0100, Lars Magne Ingebrigtsen <larsi@gnus.org> said:

Lars> Wes Hardaker <wes@hardakers.net> writes:
SY> What features do you envisage nnsourceforge having?  
>> 
>> I want something to interact with the tracking databases.  

Lars> That sounds quite useful.

Yep!

Lars> I think this could be mapped over from article marks pretty
Lars> easily.

Agreed.  Mostly.  There will be some "hacking".  My actually thought
on marks is that gnus should be somewhat extensible and should support
other marks which are backend specific.

Lars> Does Savannah use a similar interface to the tracking database
Lars> as Sourceforge does?  Then Emacs should definitely have an
Lars> interface to these databases.

Savannah is similar, but of course is not the same.  There are other
bug database types as well (samba has one called "jitterbug" that a
fair number of sites use).
-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."



  reply	other threads:[~2002-01-25 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 10:37 Pavel Janík
2002-01-12  6:08 ` Wes Hardaker
2002-01-12  6:49   ` Steve Youngs
2002-01-12 10:03     ` Kai Großjohann
2002-01-14 18:22     ` Wes Hardaker
2002-01-15  8:50       ` Kai Großjohann
2002-01-25 16:17         ` Wes Hardaker
2002-01-19 21:22       ` Lars Magne Ingebrigtsen
2002-01-25 16:20         ` Wes Hardaker [this message]
2002-01-26 22:55           ` Lars Magne Ingebrigtsen
2002-01-27  0:01             ` Daniel Pittman

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=sdsn8ucsgo.fsf@wanderer.hardakers.net \
    --to=wes@hardakers.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).