From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: esr@thyrsus.com
Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>,
Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel@gnu.org
Subject: Re: .gitignore and .bzrignore files.
Date: Mon, 24 Mar 2014 20:53:47 +0900 [thread overview]
Message-ID: <87pplbrewk.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <20140324103829.GB22737@thyrsus.com>
Eric S. Raymond writes:
> Nicolas Richard <theonewiththeevillook@yahoo.fr>:
> > I have one question : what goes in those ignore files ? I've
> > heard some people want to ignore files created during
> > compilation, while some other don't because they compile off tree
> > and want to know if files get added in the tree.
This is a tough question. However, all of the VCSes I know of provide
both cascading ignores (so that you can ignore the backup and lock
files your editor produces in a personal .ignore, and ignore the .o
produced by a C compiler in a C project and the .pyc files produced by
Python), and some way to clean up and list files that are ignored as
well as unregistered files that aren't ignored.
> Shortly I will post to the list about the complications implied by
> various ways of handling ignore files. Determining the right thing
> is not at all simple.
I'd say do what's simplest. I don't see why one can't live with a
pretty coarse approximation for a while.
next prev parent reply other threads:[~2014-03-24 11:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 20:00 Converted git repository available for review Eric S. Raymond
2014-03-21 22:00 ` Stefan
2014-03-21 22:12 ` Eric S. Raymond
2014-03-21 22:06 ` Juanma Barranquero
2014-03-22 1:00 ` Paul Eggert
2014-03-22 3:00 ` Eric S. Raymond
2014-03-22 3:37 ` Paul Eggert
2014-03-22 3:42 ` Juanma Barranquero
2014-03-22 4:29 ` Eric S. Raymond
2014-03-22 14:56 ` Paul Eggert
2014-03-22 18:47 ` Eric S. Raymond
2014-03-24 9:24 ` .gitignore and .bzrignore files Nicolas Richard
2014-03-24 10:38 ` Eric S. Raymond
2014-03-24 11:53 ` Stephen J. Turnbull [this message]
2014-03-24 15:54 ` Nicolas Richard
2014-03-24 22:44 ` Achim Gratz
2014-03-22 4:41 ` Converted git repository available for review Juanma Barranquero
2014-03-22 7:32 ` Stephen J. Turnbull
2014-03-22 7:38 ` David Kastrup
2014-03-22 7:35 ` Eli Zaretskii
2014-03-22 11:48 ` Juanma Barranquero
2014-03-22 9:12 ` Eric S. Raymond
2014-03-22 11:47 ` Juanma Barranquero
2014-03-22 9:40 ` Andreas Schwab
2014-03-22 8:02 ` Andreas Schwab
2014-03-22 9:20 ` Eric S. Raymond
2014-03-22 9:44 ` Andreas Schwab
2014-03-22 11:03 ` Eric S. Raymond
2014-03-24 22:33 ` James Cloos
2014-03-24 22:39 ` Eric S. Raymond
2014-03-25 7:57 ` David Kastrup
2014-03-25 10:54 ` Eric S. Raymond
2014-03-25 11:04 ` David Kastrup
2014-03-25 11:32 ` Eric S. Raymond
2014-03-25 11:39 ` David Kastrup
2014-03-25 11:50 ` Eric S. Raymond
2014-03-25 12:47 ` Phillip Lord
2014-03-25 13:04 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pplbrewk.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=theonewiththeevillook@yahoo.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).