Re: .gitignore and .bzrignore files.

["Eric S. Raymond" <esr@thyrsus.com>]

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.

I don't see how not excluding (for example) .o files would help with this.

> Related to this, is the fact that bzr ignores some files automatically:
> $ bzr ignore  --default-rules
> *.a
> *.o
> *.py[co]
> *.so
> *.sw[nop]
> *~
> .#*
> [#]*#
> __pycache__
> bzr-orphans

Thank you, that is information I did not have.

> Should the .bzr->.git transition automatically add these to the
> .gitignore file ?

When the .gitignore is directly translated from a .bzrignore, these
should be prepended in order to correctly emulate the behavior of the
.bzrignore file.

Paul Eggert is proposing that we not do this at all and simply drop the
.bzrignore files from the history, trusting the .gitignore files already
in place to pick up the slack.

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.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>