From: Yngve Svendsen <yngve.svendsen@sun.com>
To: "Tume Römer" <Tume.Romer@optillion.com>
Cc: help-gnats@gnu.org, Mel Hatzis <hatzis@juniper.net>
Subject: Re: Failing to connect
Date: Fri, 14 Nov 2003 08:08:00 -0000 [thread overview]
Message-ID: <3FB48CD3.6050405@sun.com> (raw)
In-Reply-To: <ED5C6BBC01A6524D919D9067AC85CDE240B7AC@exchsthlm.corp.optillion.com>
Tume Römer wrote:
> Thanks - I solved it by creating the default as suggested,
> but now I understand _what_ is happening. This should
> definitely be mentioned in the UPGRADING document.
Glad to hear you got it fixed. This should be mentioned in the docs,
yes. Anyone care to submit a fix to me? I do not have time to do this
myself right now.
Yngve Svendsen
GNATS doc guy
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-11-14 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 6:56 Tume Römer
2003-11-14 8:08 ` Yngve Svendsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 13:28 Tume Römer
2003-11-13 20:57 ` Mel Hatzis
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=3FB48CD3.6050405@sun.com \
--to=yngve.svendsen@sun.com \
--cc=Tume.Romer@optillion.com \
--cc=hatzis@juniper.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).