From: Zefram <A.Main@dcs.warwick.ac.uk>
To: hzoli@cs.elte.hu (Zoltan Hidvegi)
Subject: Re: .cvsignore files
Date: Thu, 9 May 1996 01:30:13 +0100 (BST) [thread overview]
Message-ID: <10027.199605090037@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199605082314.BAA00417@hzoli.ppp.cs.elte.hu> from "Zoltan Hidvegi" at May 9, 96 01:14:01 am
>I do not think that this is really necessary. I always build zsh in a
>separate directory so the build process does not change anything in the
>source tree with the exception of autoconf generated files. Using
>a separate build directory is always necessary in a multiplatform
>environment.
But not all of us do this. I almost never use a separate directory.
We must at least allow for the possibility.
>If one uses a separate directory then only config.h.in, configure and
>stamp-h.in remains. But config.h.in, configure and the empty stamp-h.in
>are archived in the RCS files. This is necessary since the RCS file is
>used to generate the patches between releases and not all people have
>autoconf installed on their system. And if a file is in the RCS
>distribution it should not be put into .cvsignore. After that no files
>remained :-).
The way I use CVS, any file that can be generated (including
config.h.in and stamp-h.in) does not go into the repository. In fact,
I do a "make superclean" before importing sources. I find that this is
the best way to use CVS, as one doesn't end up with redundant diffs of
generated files.
-zefram
prev parent reply other threads:[~1996-05-09 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-08 15:29 Zefram
1996-05-08 23:14 ` Zoltan Hidvegi
1996-05-09 0:30 ` Zefram [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=10027.199605090037@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=hzoli@cs.elte.hu \
/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).