From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: why does emacs (21.2.1) insist on backing up version controlled files?
Date: Tue, 29 Apr 2003 20:50:32 +0200 [thread overview]
Message-ID: <844r4hf893.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <ccd6f1a.0304290927.5f5c50ea@posting.google.com> (Aaron Hanson's message of "29 Apr 2003 10:27:20 -0700")
adh1982@yahoo.com (Aaron Hanson) writes:
> I'm setting make-backup-files and vc-make-backup-files both to
> Nil; yet I still get backups of version controlled files (ex:
> pkg.spec.~1.10.~).
See variable vc-cvs-stay-local-p.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-29 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 17:27 why does emacs (21.2.1) insist on backing up version controlled files? Aaron Hanson
2003-04-29 18:50 ` Kai Großjohann [this message]
2003-04-29 20:43 ` Aaron Hanson
2003-04-30 9:13 ` Kai Großjohann
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=844r4hf893.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.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 read-only IMAP folder(s) and NNTP newsgroup(s).