.cvsignore files

.cvsignore files

[James Kingdon]

The enclosed cleans up the "? foo" messages from CVS (in the gdb and
gdb/doc
directories).  OK to commit?

P.S. still waiting for feedback on
http://sources.redhat.com/ml/gdb-patches/2001-02/msg00161.html
- I'd like to commit that patch unless someone has an objection.
The companion patch is
http://sources.redhat.com/ml/binutils/2001-02/msg00199.html but
I'll take that one up with the binutils list unless someone here
wants to comment.

Index: gdb/.cvsignore
===================================================================
RCS file: .cvsignore
diff -N .cvsignore
--- /dev/null	Tue May  5 13:32:27 1998
+++ .cvsignore	Mon Feb 12 11:12:20 2001
@@ -0,0 +1,10 @@
+*.tab.c
+gdb
+stamp-h
+config.status
+.gdbinit
+Makefile
+config.h
+config.log
+version.c
+init.c
Index: gdb/doc/.cvsignore
===================================================================
RCS file: .cvsignore
diff -N .cvsignore
--- /dev/null	Tue May  5 13:32:27 1998
+++ .cvsignore	Mon Feb 12 11:12:20 2001
@@ -0,0 +1,5 @@
+*.info*
+config.status
+GDBvn.texi
+Makefile
+config.log

Re: .cvsignore files

[Michael Snyder]

James Kingdon wrote:
> 
> The enclosed cleans up the "? foo" messages from CVS (in the gdb and
> gdb/doc
> directories).  OK to commit?

I don't get it.  All of these files go into the build directory.
Are you building in the source directory?

> 
> P.S. still waiting for feedback on
> http://sources.redhat.com/ml/gdb-patches/2001-02/msg00161.html
> - I'd like to commit that patch unless someone has an objection.
> The companion patch is
> http://sources.redhat.com/ml/binutils/2001-02/msg00199.html but
> I'll take that one up with the binutils list unless someone here
> wants to comment.
> 
> Index: gdb/.cvsignore
> ===================================================================
> RCS file: .cvsignore
> diff -N .cvsignore
> --- /dev/null   Tue May  5 13:32:27 1998
> +++ .cvsignore  Mon Feb 12 11:12:20 2001
> @@ -0,0 +1,10 @@
> +*.tab.c
> +gdb
> +stamp-h
> +config.status
> +.gdbinit
> +Makefile
> +config.h
> +config.log
> +version.c
> +init.c
> Index: gdb/doc/.cvsignore
> ===================================================================
> RCS file: .cvsignore
> diff -N .cvsignore
> --- /dev/null   Tue May  5 13:32:27 1998
> +++ .cvsignore  Mon Feb 12 11:12:20 2001
> @@ -0,0 +1,5 @@
> +*.info*
> +config.status
> +GDBvn.texi
> +Makefile
> +config.log

Re: .cvsignore files

[Andrew Cagney]

James Kingdon wrote:
> 
> The enclosed cleans up the "? foo" messages from CVS (in the gdb and
> gdb/doc
> directories).  OK to commit?

Humor me.

This change just affects the list of things that CVS ignores when you do
a `cvs update`.  You;re creating new .cvsignore files in the gdb/ and
gdb/doc/ directories that list the files generated in a build.

Per michael's e-mail I'm puzzled as to their usefulness as people are
encouraged to build using a separate build tree.
What puzzles me even more is the absence of any of tm.h xm.h or nm.h in
that list.

How were the files in that list selected?

	Andrew