From: Andrew Cagney <ac131313@cygnus.com>
To: James Kingdon <jkingdon@cthulhu.engr.sgi.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: .cvsignore files
Date: Thu, 15 Feb 2001 16:18:00 -0000 [thread overview]
Message-ID: <3A8C70C7.12A5250C@cygnus.com> (raw)
In-Reply-To: <3A884225.D86D43EC@engr.sgi.com>
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
prev parent reply other threads:[~2001-02-15 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 12:06 James Kingdon
2001-02-12 12:14 ` Michael Snyder
2001-02-15 16:18 ` Andrew Cagney [this message]
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=3A8C70C7.12A5250C@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jkingdon@cthulhu.engr.sgi.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox