From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: OT: CVS .#* files
Date: Tue, 17 Oct 2000 16:39:52 +0200 (MET DST) [thread overview]
Message-ID: <200010171439.QAA10259@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 17 Oct 2000 18:34:58 +0400
Andrej Borsenkow wrote:
> I discovered the whole bunch of files that look like .#Makefile.in.1.4 etc
> etc.. Are they needed or can I delete them? Should not they be cleaned up
> automatically by CVS?
They are created by cvs as backup files when it has to merge changes
from the repository with local changes.
You can delete them if all conflicts have been resolved, which they
probably have.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-10-17 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 14:39 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-17 14:34 Andrej Borsenkow
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=200010171439.QAA10259@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).