On 14 May 2012 11:08, Martin Schreiber <mse00...@gmail.com> wrote: > On Monday 14 May 2012 10:32:03 IvankoB wrote: >> > Do you know the ".gitignore" file? >> >> Project wide too ? What for this doubling.. >> > Valid for the directory and subdirectories without ".gitignore" files. You > should not touch the files in ".git", it is better to use git commands to > change settings.
Let me explain the difference between those two files. '.gitignore' files are for a specific directory (and recursive from that point) and you can have many of them in your project hierarchy. Now importantly, you can have this file added to the git repository too (being a tracked file, just like your source code). So everybody working on a project share the same .gitignore files. These files are often used to recreate a directory hierarchy too - because currently git cannot track a empty directory (eg: like SubVersion can). The .git/info/exclude file is meant as a "private exclude" file and can't be committed to the repository. So the rules in that file apply to the whole project, but only to that specific machine. Both files have the same syntax format, which is very simple, and no you don't need the git tools to edit that file. Neither of those files can break a repository. -- Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://fpgui.sourceforge.net ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
