From: "Dan Elliott" <dan_elliott_at_cox_dot_net@noSpam.org>
Subject: Re: ange-ftp and version control
Date: Tue, 30 Nov 2004 05:20:52 -0600 [thread overview]
Message-ID: <FHYqd.1$vW6.0@dfw-service2.ext.ray.com> (raw)
In-Reply-To: pan.2004.11.29.23.31.58.548645@spam_is_pathetic.com
nevermind. i am now using TRAMP. It is very nice!
"Daniel L Elliott" <dan_elliott_at_cox_dot_net@spam_is_pathetic.com> wrote
in message news:pan.2004.11.29.23.31.58.548645@spam_is_pathetic.com...
> On Mon, 29 Nov 2004 17:27:37 -0600, Daniel L Elliott wrote:
>
> > Hello,
> >
> > I want to use both ange-ftp and version control. As far as I am
> > concerned, the version control files can be either local or remote.
> >
> > I have already set rcs-ange-ftp-ignore to nil. However, the
> > RCS-registered files on the remote machine are not associated with RCS
by
> > emacs.
> >
> > Thank you,
> >
> > dan elliott
>
>
> Can I modify ange to use sftp?
prev parent reply other threads:[~2004-11-30 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 23:27 ange-ftp and version control Daniel L Elliott
2004-11-29 23:31 ` Daniel L Elliott
2004-11-30 11:20 ` Dan Elliott [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='FHYqd.1$vW6.0@dfw-service2.ext.ray.com' \
--to=dan_elliott_at_cox_dot_net@nospam.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).