I don't mind either way.
I have found it generally useful to have them provided, and have wished the plib would
do the same (for .deps directories, in particular).
However, I have only ever worked on small patches, never adding files, so I have never
needed to take note of the ? and unknown
[EMAIL PROTECTED] wwrites:
I have found it generally useful to have them provided, and
have wished the plib would do the same (for .deps directories,
in particular).
FYI
the FlightGear 'configure' is designed to be able to be run in
a directory other then then the CVS source tree.
This has
FYI
the FlightGear 'configure' is designed to be able to be run in
a directory other then then the CVS source tree.
That sounds well worth a try. Thanks.
This has several advantages amongst them keeping the source
tree MUCH cleaner :-)
And being able to keep a debug build and a release
du 26/06/2002 13:07
De : [EMAIL PROTECTED]
A : [EMAIL PROTECTED]
Copie ? :
Objet : Re: [Flightgear-devel] Remove .cvsignore?
Frederic Bouvier writes:
What is the rational of doing that ?
To let people create their own, local, customized .cvsignore files
instead (those who care
Cameron Moore writes:
Personally, I agree with Fred. The number of people who will actually
be using a custom cvsignore will be far fewer than those of us who will
not.
That seems to be the consensus -- I won't remove them.
All the best,
David
--
David Megginson, [EMAIL PROTECTED],
