On 08/22/2012 03:03 PM, David Linn wrote:
> Hi,
>
> I was wondering how to maintain a git branch where I can test things out.
> Running bootstrap and configure generate a bunch of extra files. Do these
> files need to be tracked ? Can I just put all of them in .gitignore ? I'm
> new to git (version control itself actually) so I'm unsure of the workflow.
The contents of .gitignore are indeed very, very sparse.
When I was working with İlim on a branch of wget, at some point I added
the following contents to .git/info/exclude (which is similar to
.gitignore, but is an untracked file).
Someone should perhaps drop something similar into the real .gitignore :)
BTW, if you're new to both git and version control, I heartily recommend
the O'Reilly book. Realize that git differs somewhat substantially, in
its details, from other version control systems. There are also a couple
sets of words whose meanings are exactly reversed in the version control
system named Mercurial ("pull" and "fetch", and also the term HEAD means
something different in git than it does in Mercurial).
*.[oa]
*~
*.po
*.gmo
Makefile
/.gitignore
/.version
/config.log
/config.status
/INSTALL
/Makefile.in
/aclocal.m4
/autom4te.cache/
/doc/Makefile.in
/doc/sample.wgetrc.munged_for_texi_inclusion
/doc/stamp-vti
/doc/version.texi
/doc/wget.1
/doc/wget.info
/doc/wget.pod
/src/Makefile.in
/src/config.h.in
/tests/Makefile.in
/util/Makefile.in
/po/Makefile.in
/po/Makevars
/po/POTFILES
/po/wget.pot
/po/.reference/
/po/.gitignore
/m4/.gitignore
/m4/gnulib-cache.m4
/lib/
/gnulib/
/build-aux/.gitignore
/build-aux/compile
/build-aux/config.guess
/build-aux/config.sub
/build-aux/depcomp
/build-aux/install-sh
/build-aux/mdate-sh
/build-aux/missing
/build-aux/snippet/
/build-aux/texinfo.tex
/configure
/po/LINGUAS
/src/.deps/
/src/build_info.c
/src/config.h
/src/css.c
/src/css_.c
/src/stamp-h1
/src/version.c
/src/wget
/tests/WgetTest.pm
