William Stein <wst...@gmail.com> writes: > On Sun, Feb 19, 2012 at 9:38 PM, Keshav Kini <keshav.k...@gmail.com> wrote: >> Hope that helps. Evidently other people in this thread do not know that >> I have been maintaining a git version of the Sage library, so hopefully >> it will help them too, if they're interested :) > > Can we add a better .gitignore? > > git status > ... > # Untracked files: > # (use "git add <file>..." to include in what will be committed) > # > # ../../../../build/ > # ../../../../c_lib/.sconsign.dblite > # ../../../../c_lib/libcsage.dylib > # ../../../../c_lib/src/ZZ_pylong.os > # ../../../../c_lib/src/convert.os > # ../../../../c_lib/src/gmp_globals.os > # ../../../../c_lib/src/interrupt.os > # ../../../../c_lib/src/memory.os > # ../../../../c_lib/src/mpn_pylong.os > # ../../../../c_lib/src/mpz_longlong.os > and a *LOT* more...
Yes, we definitely should make a .gitignore once we actually start moving to git, or even earlier. But I think that this time we should make sure lines in the .gitignore file are commented to mention why we're ignoring certain things, unlike how the .hgignore file is now. "Boring file regexps" and "sage files to ignore" is not good enough, especially for newbie developers :) Anyway, for now, you can do $ cd $SAGE_ROOT/devel/sage $ git config status.showUntrackedFiles no This will, as the name of the config variable suggests, stop unknown files from appearing in the `git status` report. Of course, this also means that you won't notice if you write a new file and forget to add it, but if you always use the -v option with `git commit` to check what you're committing, this shouldn't be a problem. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
