You can always delete everything that is not under version control. Thats the point of it. Run "git clean -f" to do it automatically.
On Thursday, April 9, 2015 at 5:25:01 PM UTC+2, kcrisman wrote: > > >> >> From the rc1 thread: >> >> >> On 03/30/2015 03:15 PM, Jeroen Demeyer wrote: >> > On 2015-03-30 10:28, Simon King wrote: >> >> But how did they come there? I thought that meanwhile there is a >> >> separate folder for compiling Sage code. >> > Those files still date from the time when there wasn't a separate >> > folder. You can safely delete them. >> > > Ok. Followup: > > # src/sage/tests/cython.c > # src/sage/tests/interrupt.c > # src/sage/tests/stl_vector.cpp > > $ ls -r src/sage/tests/*.c > src/sage/tests/interrupt.c src/sage/tests/c_lib.c > src/sage/tests/cython.c > $ ls -r src/sage/tests/*.cpp > src/sage/tests/stl_vector.cpp > > Apparently there is an extra .c file that isn't in the git list. I'm > hesitant to remove ALL .c, .h, and .cpp files unless I'm sure they are all > unneeded... but I don't see how to identify the ones that aren't in that > list. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
