zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: A.Main@dcs.warwick.ac.uk (Zefram)
Cc: zsh-workers@math.gatech.edu
Subject: Re: .cvsignore files
Date: Thu, 9 May 1996 01:14:01 +0200 (MET DST)	[thread overview]
Message-ID: <199605082314.BAA00417@hzoli.ppp.cs.elte.hu> (raw)
In-Reply-To: <3606.199605081529@cray.dcs.warwick.ac.uk> from Zefram at "May 8, 96 04:29:30 pm"

> The patch below adds a full complement of .cvsignore files.  These are
> essential for those of us using CVS, and take up very little space.
> They really should be included in the distribution because a significant
> number of people need them and they really have to go into the repository
> to be of full use.

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.

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 :-).

Zoltan



  reply	other threads:[~1996-05-09  0:14 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 [this message]
1996-05-09  0:30   ` Zefram

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=199605082314.BAA00417@hzoli.ppp.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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).