From: Gary Thomas <gthomas@ecoscentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: policy on .cvsignore files
Date: Thu, 08 Aug 2002 09:32:00 -0000 [thread overview]
Message-ID: <1028824361.3110.269.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20020808162922.GL4644@biferten.ma.tech.ascom.ch>
On Thu, 2002-08-08 at 10:29, Andrew Lunn wrote:
> Hi Folks
>
> Is there any policy on .cvsignore files? There are none at the moment.
>
> One would be nice in doc/sgml. All the html files are built there,
> plus a few intermediary files. These should be ignored by cvs.
>
By all means, add them, especially if it makes your life easier.
--
------------------------------------------------------------
Gary Thomas |
eCosCentric, Ltd. |
+1 (970) 229-1963 | eCos & RedBoot experts
gthomas@ecoscentric.com |
http://www.ecoscentric.com/ |
------------------------------------------------------------
prev parent reply other threads:[~2002-08-08 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 9:29 Andrew Lunn
2002-08-08 9:32 ` Gary Thomas [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=1028824361.3110.269.camel@hermes.chez-thomas.org \
--to=gthomas@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).