public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Jamin W. Collins" <jcollins@asgardsrealm.net>
To: help-gnats@gnu.org
Subject: Re: send-pr error!
Date: Fri, 14 Dec 2001 08:34:00 -0000	[thread overview]
Message-ID: <1008347309.17203.2.camel@Cerberus> (raw)
Message-ID: <20011214083400.UTWxDjo6loDTBh_lVm-HWeryT9p_j-Cfypaez_9o21U@z> (raw)
In-Reply-To: <20011214161957.GA21056@wookimus.net>

On Fri, 2001-12-14 at 10:19, Chad C. Walstrom wrote:
> <rant>I don't know what the developers of sourceforge were thinking when
> they excluded a search function for their "bugtracking" module!</rant>
> 
> <plug>Do you think the people developing Savannah would be interested in
> using gnats? *grin*</plug>

First the product would need to install and work with a web interface. 
From my experience so far (see previous posts) it does not.

Note: I'm not saying that my problems are related directly to the
product, rather that in my experience there are problems that have yet
to be resolved.

Jamin W. Collins


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

  parent reply	other threads:[~2001-12-14  8:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 10:23 Chad C. Walstrom
2001-11-08 10:23 ` Yngve Svendsen
2001-11-08 13:08   ` Chad C. Walstrom
2001-11-09 18:10     ` Milan Zamazal
2001-12-15  7:24       ` Milan Zamazal
2002-01-17 19:14       ` Hugo Gayosso
2001-12-14 11:17     ` Chad C. Walstrom
2001-12-14  9:28   ` Yngve Svendsen
2001-11-08 10:23 ` Jamin W. Collins [this message]
2001-11-08 13:05   ` Chad C. Walstrom
2001-11-08 18:22     ` Jamin W. Collins
2001-11-09  2:55       ` Chad C. Walstrom
2001-11-09 14:16         ` Jamin W. Collins
2001-11-09 14:17           ` Yngve Svendsen
2001-12-15  2:54             ` Yngve Svendsen
2001-11-10  2:46           ` Milan Zamazal
2001-11-12 10:40             ` My inability to configure Gnats(web)4 (was send-pr error!) Jamin W. Collins
2001-11-12 11:28               ` Jamin W. Collins
2001-11-17 13:06                 ` Jamin W. Collins
2001-12-22 13:41                   ` Jamin W. Collins
2001-12-16  8:37                 ` Jamin W. Collins
2001-12-15  8:36               ` Jamin W. Collins
2001-12-15  7:24             ` send-pr error! Milan Zamazal
2001-12-14 20:45           ` Jamin W. Collins
2001-12-14 15:24         ` Chad C. Walstrom
2001-12-14 11:39       ` Jamin W. Collins
2001-12-14 10:55     ` Chad C. Walstrom
2001-12-14  8:34   ` Jamin W. Collins
2001-12-14  8:27 ` Chad C. Walstrom
  -- strict thread matches above, loose matches on Subject: below --
2001-11-06  9:23 Choi, Jang-Wook
2001-11-06  9:25 ` Yngve Svendsen
2001-11-12 10:06   ` Milan Zamazal
2001-11-12 10:40     ` Yngve Svendsen
2001-11-18 19:55       ` Milan Zamazal
2001-12-23 12:36         ` Milan Zamazal
2001-12-15 10:52       ` Yngve Svendsen
2001-12-15  7:24     ` Milan Zamazal
2001-12-14  3:09   ` Yngve Svendsen
2001-12-14  0:43 ` Choi, Jang-Wook

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=1008347309.17203.2.camel@Cerberus \
    --to=jcollins@asgardsrealm.net \
    --cc=help-gnats@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).