[git] An ignore file for the top-level repository?
I cloned a copy of the git version of the top-level Boost repository, which recursively added the individual libraries. The directions added two commands to run boot-strapping and build scripts. I had to set up an ".gitignore" file so the GUI GitHub app won't complain about those synthesized files. Shouldn't there already be an ignore file there that does this? (You only list the top-level files & directories; nested files automatically get ignored too.) I couldn't sync (i.e. upload) the ignore-file since I don't have write access for the top-level repository. So I'll get a conflict once someone does add an ignore file for everyone? Daryle W.
On 7 January 2014 11:36, Daryle Walker wrote:
I couldn't sync (i.e. upload) the ignore-file since I don't have write access for the top-level repository. So I'll get a conflict once someone does add an ignore file for everyone?
You could list the ignored files in .git/info/exclude instead, so you wouldn't get a conflict if a .gitignore is added later, but it does seem like someone should add the top-level .gitignore instead.
On 01/07/2014 05:36 AM, Daryle Walker wrote:
I cloned a copy of the git version of the top-level Boost repository, which recursively added the individual libraries. The directions added two commands to run boot-strapping and build scripts. I had to set up an ".gitignore" file so the GUI GitHub app won't complain about those synthesized files. Shouldn't there already be an ignore file there that does this? (You only list the top-level files & directories; nested files automatically get ignored too.) I couldn't sync (i.e. upload) the ignore-file since I don't have write access for the top-level repository. So I'll get a conflict once someone does add an ignore file for everyone?
An alternative to using .gitignore (which is in the controlled directories) is to edit .git/info/exclude (which is private to the workspace, and will not conflict with upstream additions/removals/changes to a .gitignore file). I have no idea if GitHub's GUI application provides access to that file, though. I would prefer that these files not be added to a new .gitignore in the superproject. I find it convenient to be able to do "git clean -fd ." to remove all the derived files; the equivalent of "make distclean" in other systems. If those files are in .gitignore, I have to use "git clean -fdx ." which is far more likely to delete something I care about (e.g., a TODO list that I'd put in my .git/info/exclude). Peter
Hi Daryle, On Tuesday, 7. January 2014 06:36:28 Daryle Walker wrote:
I cloned a copy of the git version of the top-level Boost repository, which recursively added the individual libraries. The directions added two commands to run boot-strapping and build scripts. I had to set up an ".gitignore" file so the GUI GitHub app won't complain about those synthesized files. Shouldn't there already be an ignore file there that does this? (You only list the top-level files & directories; nested files automatically get ignored too.) I couldn't sync (i.e. upload) the ignore-file since I don't have write access for the top-level repository.
I've already created a pull request for this https://github.com/boostorg/boost/pull/2
So I'll get a conflict once someone does add an ignore file for everyone?
Yes, you get a merge conflict (or a clean merge) if you committed it locally. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany
participants (4)
-
Daryle Walker -
Jonathan Wakely -
Jürgen Hunold -
Peter A. Bigot