Re: [Ekiga-devel-list] Git ignorance file

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

Julien Puydt wrote:
> Hi,
>
> since I didn't know about .gitignore, I used .git/info/exclude, and put 
> this :
> *.[oa]
> *~
> Makefile.in
> Makefile
> *.lo
> *.loT
> *.la
> *.gmo
> .deps
> aclocal.m4
> autom4te.cache
> config.*
> configure
> missing
> mkinstalldirs
> depcomp
> install-sh
> libtool
> ltmain.sh
> gnome-doc-utils.make
> intltool-*
> help/*/*mo
> help/*/*xml
> help/*.omf
> lib/engine/components/hal-dbus/hal-marshal.c
> lib/engine/components/hal-dbus/hal-marshal.h
> pixmaps/inlines.h
> ekiga.desktop*
> ekiga.schemas
> ekiga.schemas.in
> src/ekiga
> src/ekiga-snapshot
> src/ekiga-config-tool
> src/ekiga-helper
> po/.intltool-merge-cache
> po/Makefile.in.in
> po/POTFILES
> po/stamp-it
> stamp-h1
> Doxyfile
> lib/pixops/timescale
> src/dbus-helper/dbus-stub.h
> src/dbus-helper/dbus-helper-stub.h
> src/dbus-helper/org.ekiga.*.service
> revision.h
> src/build-subdir-stamp
>
>
> As you see, it is much, much shorter than the current .gitignore... but 
> perhaps one cannot use wildcards in that later file?

Exactly.  man gitignore:
       Which file to place a pattern in depends on how the pattern is 
meant to be used.
       Patterns which should be version-controlled and distributed to 
other repositories via
       clone (i.e., files that all developers will want to ignore) 
should go into a
       .gitignore file. Patterns which are specific to a particular 
repository but which do
       not need to be shared with other related repositories (e.g., 
auxiliary files that live
       inside the repository but are specific to one user’s workflow) 
should go into the
       $GIT_DIR/info/exclude file. Patterns which a user wants git to 
ignore in all
       situations (e.g., backup or temporary files generated by the 
user’s editor of choice)
       generally go into a file specified by core.excludesfile in the 
user’s ~/.gitconfig.

--
Eugen