From: Hannu Koivisto <azure@iki.fi>
Subject: Re: Suboptimal use of ~/.authinfo
Date: 02 Mar 2001 16:55:39 +0200 [thread overview]
Message-ID: <87pug0dxuc.fsf@lynx.ionific.com> (raw)
In-Reply-To: <vaf4rxc8k9z.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "02 Mar 2001 12:47:36 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
| If you use the machine more often, why don't you make an entry in the
| server buffer and then just do `RET' in the server buffer?
Good point, for some reason I didn't realize to try it (there
already is an entry, I just didn't realize to use the server buffer
to begin with).
Thanks,
--
Hannu
Please don't send copies of list mail
prev parent reply other threads:[~2001-03-02 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 9:38 Hannu Koivisto
2001-03-02 11:47 ` Kai Großjohann
2001-03-02 14:55 ` Hannu Koivisto [this message]
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=87pug0dxuc.fsf@lynx.ionific.com \
--to=azure@iki.fi \
/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).