On Mon, Apr 20, 2009 at 4:56 PM, Behdad Esfahbod <beh...@behdad.org> wrote: > On 04/20/2009 02:34 AM, Steve Frécinaux wrote: >> >> Behdad Esfahbod wrote: >>> >>> The idea is that .gitignore files are autogenerated and are NOT stored >>> in the repository. To use, just copy git.mk into your toplevel, add it >>> to git, run "make -f git.mk" and commit all changes it makes to your >>> tree... >> >> If the generated .gitignore is not meant to be committed into the >> repository, maybe the script should edit .git/info/exclude instead ? > > Why? Other than being harder to generate (since current scheme generates > per-dir .gitignore files) and generally a bad idea to touch the .git dir, > "man gitignore" also suggests that that's the wrong place: > > > "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."
Yeap, per-repository (local) include files should go to $GIT_DIR/info/exclude. -- Felipe Contreras _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
