This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Non-source files in CVS

To: Marius Vollmer <mvo at zagadka dot ping dot de>
Subject: Re: Non-source files in CVS
From: Jost Boekemeier <jostobfe at linux dot zrz dot TU-Berlin dot DE>
Date: 17 Jan 2000 21:01:06 +0100
Cc: "Greg J. Badros" <gjb at cs dot washington dot edu>, guile at sourceware dot cygnus dot com
References: <87wvpivjby.fsf@zagadka.ping.de> <qrrso06iv2h.fsf@clavicle.cs.washington.edu> <87g0w5ae73.fsf@zagadka.ping.de>

Marius Vollmer <mvo@zagadka.ping.de> writes:

> I think we can use `$CVSROOT/CVSROOT/cvsignore' and leave .cvsignore
> to the user.  It looks like Guile has its own repository, so it should
> be no major problem that `$CVSROOT/CVSROOT/cvsignore' is
> per-repository and not per-module.

Can cvs users access the file $CVSROOT/CVSROOT/cvsignore by using cvs
commands?  If not, how can you tell the users which files are created
by the build process and should be ignored?

Of course I can run cvs co, capture the state of all subdirs compare
them with the state after configure/make and create my own
.cvsignore's by using a script.

Jost

Follow-Ups:
- Re: Non-source files in CVS
  - From: Greg J. Badros
- Re: Non-source files in CVS
  - From: Maciej Stachowiak

References:
- Non-source files in CVS
  - From: Marius Vollmer
- Re: Non-source files in CVS
  - From: Greg J. Badros
- Re: Non-source files in CVS
  - From: Marius Vollmer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]