Hi Bruno,
Bruno Haible writes:
> Yes please.
>
>> Not sure if there was a reason for keeping them after moving to git.
>
> There was a CVS mirror of the git repository for a while, after we moved
> to git. But by now, it's surely dead (or irrelevant) for a long time.
Thanks. Removed them [1].
Hi Collin,
> Can these files be removed?
>
> $ find . -name '.cvsignore'
> ./.cvsignore
> ./doc/.cvsignore
> ./lib/.cvsignore
> ./m4/.cvsignore
Yes please.
> Not sure if there was a reason for keeping them after moving to git.
There was
Can these files be removed?
$ find . -name '.cvsignore'
./.cvsignore
./doc/.cvsignore
./lib/.cvsignore
./m4/.cvsignore
Not sure if there was a reason for keeping them after moving to git.
Collin
-tool. This will solve half of your problem.
The other half is that you have files generated from "make" while you perform
VCS operations, and you wish them to be added to .cvsignore or .gitignore.
That is an issue you should bring up with the automake developers, IMO. If
you were dev
"make" while you perform
> VCS operations, and you wish them to be added to .cvsignore or .gitignore.
> That is an issue you should bring up with the automake developers, IMO. If
> you were developing packages without gnulib, that use the automake
> BUILT_SOURCES variable, yo
o gnulib-tool. This will solve half of your problem.
The other half is that you have files generated from "make" while you perform
VCS operations, and you wish them to be added to .cvsignore or .gitignore.
That is an issue you should bring up with the automake developers, IMO. If
you w
I've just noticed for the first time that these files (or at least
.gitignore, assuming that .cvsignore works the same way) have rather odd
contents.
There seem to be basically two classes of user when it comes to what is
ignored:
1. gnulib is considered as a build dependency, so no
Jim Meyering wrote:
> Would you be interested in a gnulib-tool patch to add an option so that
> a project that version-controls the sources does not get the primary
> sources listed in the generated .gitignore and .cvsignore files?
The discussion in the thread "Updating a package&
Hi Bruno,
Would you be interested in a gnulib-tool patch to add an option so that
a project that version-controls the sources does not get the primary
sources listed in the generated .gitignore and .cvsignore files?
Of course, including names of derived files (like .h from .h.in) is
still useful
Karl Berry wrote:
> Should there be a gnulib/uniwidth/.cvsignore file for .deps (and
> .dirstamp?), as with gnulib/lib/.cvsignore?
Indeed, this will make gnulib-tool a little bit more comfortable. I'm
applying this:
2007-07-23 Bruno Haible <[EMAIL PROTECTED]>
10 matches
Mail list logo
