From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: More .cvsignore entries?
Date: Mon, 15 Jul 2002 10:13:25 -0400 [thread overview]
Message-ID: <200207151413.g6FEDPk24472@rum.cs.yale.edu> (raw)
In-Reply-To: vaf3cumhypo.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de
> | In directory .:
> | In directory info:
> | Unknown info/elisp-covers.texi
> | Unknown info/elisp-vol1.texi
> | Unknown info/elisp-vol2.texi
Where do they come from ? Why don't you just delete them ?
If they come back, it's a bug somewhere and we should fix it instead
of hiding the problem by adding them to .cvsignore.
Note that my info/.cvsignore contains just * since all the files
in there are auto-generated (except for the `dir' file, but I also
auto-generate it, even though the result is less good).
> | In directory lisp:
> | Modified lisp/cus-load.el
> | Modified lisp/finder-inf.el
> | Modified lisp/loaddefs.el
These are under CVS so there is no reason to put them in .cvsignore.
> | In directory man:
> | Unknown man/emacs.op
> | Unknown man/emacs.ops
I don't have those here, so maybe it's only generated by some
other version of TeXinfo. Can you check if that's indeed the case
and if so add *.op and *.ops to the man/.cvsignore file ?
Stefan
next prev parent reply other threads:[~2002-07-15 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 19:54 More .cvsignore entries? Kai Großjohann
2002-07-15 9:49 ` Richard Stallman
2002-07-15 11:55 ` Robert J. Chassell
2002-07-15 12:14 ` Kai Großjohann
2002-07-15 16:21 ` Eli Zaretskii
2002-07-16 16:27 ` Richard Stallman
2002-07-15 14:13 ` Stefan Monnier [this message]
2002-07-15 19:51 ` Kai Großjohann
2002-07-15 20:10 ` Stefan Monnier
2002-07-16 4:42 ` Eli Zaretskii
2002-07-16 12:28 ` Robert J. Chassell
2002-07-16 14:17 ` Kai Großjohann
2002-07-16 15:21 ` Template for GFDL copying Robert J. Chassell
2002-07-16 16:18 ` More .cvsignore entries? Eli Zaretskii
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=200207151413.g6FEDPk24472@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).