nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-27 13:53:31 +01:00
Code Issues Packages Projects Releases Wiki Activity
703ad69587
tor/.gitignore

183 lines
2.9 KiB
Plaintext
Raw Normal View History

Add foo.o and foo~ files to gitignore.
2009-04-29 20:00:14 +02:00
# Editor droppings
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
\#*\#
.#*
Add foo.o and foo~ files to gitignore.
2009-04-29 20:00:14 +02:00
*~
Add *.swp to .gitignore as vim's editor dropping.
2009-05-27 18:10:37 +02:00
*.swp
Add foo.o and foo~ files to gitignore.
2009-04-29 20:00:14 +02:00
# C stuff
*.o
Add some MSVC stuff to gitignore
2012-05-14 18:35:10 +02:00
*.obj
Add foo.o and foo~ files to gitignore.
2009-04-29 20:00:14 +02:00
# Diff droppings
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
*.orig
*.rej
# gcov stuff
*.gcno
*.gcov
*.gcda
# latex stuff
*.aux
*.dvi
*.blg
*.bbl
*.log
# Autotools stuff
.deps
Update .gitignore with new autotools droppings from nonrecursive make
2012-08-27 16:11:55 +02:00
.dirstamp
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# Stuff made by our makefiles
*.bak
Add new ntor bits to gitignore
2012-12-08 06:57:19 +01:00
# Python droppings
*.pyc
Deal with the aftermath of sorting contrib This basically amounts to grepping for every file that mentioned contrib and adjusting its references to refer to the right place.
2014-04-28 17:59:55 +02:00
*.pyo
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# /
/Makefile
/Makefile.in
/aclocal.m4
/autom4te.cache
/build-stamp
Add 'compile' to .gitignore
2010-09-30 22:41:12 +02:00
/compile
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/configure
/Doxyfile
/orconfig.h
/orconfig.h.in
/config.cache
/config.log
/config.status
/config.guess
/config.sub
/conftest*
Update .gitignore with new autotools droppings from nonrecursive make
2012-08-27 16:11:55 +02:00
/micro-revision.*
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/patch-stamp
/stamp-h
/stamp-h.in
/stamp-h1
Add a new automake dropping ("test-driver") to .gitignore
2013-01-16 07:56:35 +01:00
/test-driver
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/tor.sh
/tor.spec
/depcomp
/install-sh
/missing
/mkinstalldirs
/Tor*Bundle.dmg
/tor-*-win32.exe
# /contrib/
Deal with the aftermath of sorting contrib This basically amounts to grepping for every file that mentioned contrib and adjusting its references to refer to the right place.
2014-04-28 17:59:55 +02:00
/contrib/dist/tor.sh
/contrib/dist/torctl
/contrib/operator-tools/tor.logrotate
/contrib/dist/suse/tor.sh
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# /debian/
/debian/files
Build debian's micro-revision into the binary If we have a debian/micro-revision.i, replace the one in src/or with our copy so that this will be the revision that ends up in the binary. This is an informational only version string, but it'd be kinda nice if it was (more) accurate nonetheless. Of course this won't help if people manually patch around but it's still preferable to claiming we are exactly upstream's source. If we are building directly out of a git tree, update debian/micro-revision.i in the clean target.
2009-09-21 14:51:26 +02:00
/debian/micro-revision.i
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/debian/patched
/debian/tor
/debian/tor.postinst.debhelper
/debian/tor.postrm.debhelper
/debian/tor.prerm.debhelper
/debian/tor.substvars
# /doc/
/doc/Makefile
/doc/Makefile.in
/doc/doxygen
Convert the Tor manpage to asciidoc. This should be a very faithful conversion, preserving as much of the layout of the old manpage as possible. This wasn't possible for the nt-service and the DataDirectory/state parts. See a later commit for some small cleanups. Tiago Faria helped with the asciidoc conversion, big thanks!
2010-01-19 14:53:38 +01:00
/doc/tor.1
/doc/tor.1.in
/doc/tor.html
/doc/tor.html.in
add a2x intermediate files to gitignore
2010-02-01 04:53:40 +01:00
/doc/tor.1.xml
Add more tor-fw-helper files to gitignore
2010-09-30 23:10:37 +02:00
/doc/tor-fw-helper.1
/doc/tor-fw-helper.1.in
/doc/tor-fw-helper.html
/doc/tor-fw-helper.html.in
/doc/tor-fw-helper.1.xml
Convert the tor-gencert manpage to asciidoc
2010-01-18 08:42:48 +01:00
/doc/tor-gencert.1
/doc/tor-gencert.1.in
/doc/tor-gencert.html
/doc/tor-gencert.html.in
add a2x intermediate files to gitignore
2010-02-01 04:53:40 +01:00
/doc/tor-gencert.1.xml
Convert the tor-resolve manpage to asciidoc
2010-01-19 14:51:10 +01:00
/doc/tor-resolve.1
/doc/tor-resolve.1.in
/doc/tor-resolve.html
/doc/tor-resolve.html.in
add a2x intermediate files to gitignore
2010-02-01 04:53:40 +01:00
/doc/tor-resolve.1.xml
Convert the torify manpage to asciidoc
2010-01-19 04:35:04 +01:00
/doc/torify.1
/doc/torify.html
add a2x intermediate files to gitignore
2010-02-01 04:53:40 +01:00
/doc/torify.1.xml
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# /doc/spec/
/doc/spec/Makefile
/doc/spec/Makefile.in
# /src/
/src/Makefile
/src/Makefile.in
# /src/common/
/src/common/Makefile
/src/common/Makefile.in
Command-line option to dump SHA1 digests of all source files. Now, when you call tor --digests, it dumps the SHA1 digest of each source file that Tor was built with. We support both 'sha1sum' and 'openssl sha1'. If the user is building from a tarball and they haven't edited anything, they don't need any program that calculates SHA1. If they _have_ modified a file but they don't have a program to calculate SHA1, we try to build so we do not output digests.
2009-01-04 03:43:05 +01:00
/src/common/common_sha1.i
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/src/common/libor.a
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
/src/common/libor-testing.a
Add some MSVC stuff to gitignore
2012-05-14 18:35:10 +02:00
/src/common/libor.lib
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/src/common/libor-crypto.a
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
/src/common/libor-crypto-testing.a
Add some MSVC stuff to gitignore
2012-05-14 18:35:10 +02:00
/src/common/libor-crypto.lib
Update Tor to use Libevent 2.0 APIs when available. This patch adds a new compat_libevent.[ch] set of files, and moves our Libevent compatibility and utilitity functions there. We build them into a separate .a so that nothing else in src/commmon depends on Libevent (partially fixing bug 507). Also, do not use our own built-in evdns copy when we have Libevent 2.0, whose evdns is finally good enough (thus fixing Bug 920).
2009-06-04 07:05:23 +02:00
/src/common/libor-event.a
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
/src/common/libor-event-testing.a
Add some MSVC stuff to gitignore
2012-05-14 18:35:10 +02:00
/src/common/libor-event.lib
Add new ntor bits to gitignore
2012-12-08 06:57:19 +01:00
/src/common/libcurve25519_donna.a
/src/common/libcurve25519_donna.lib
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# /src/config/
/src/config/Makefile
/src/config/Makefile.in
/src/config/sample-server-torrc
/src/config/torrc
/src/config/torrc.sample
# /src/or/
/src/or/Makefile
/src/or/Makefile.in
Command-line option to dump SHA1 digests of all source files. Now, when you call tor --digests, it dumps the SHA1 digest of each source file that Tor was built with. We support both 'sha1sum' and 'openssl sha1'. If the user is building from a tarball and they haven't edited anything, they don't need any program that calculates SHA1. If they _have_ modified a file but they don't have a program to calculate SHA1, we try to build so we do not output digests.
2009-01-04 03:43:05 +01:00
/src/or/or_sha1.i
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/src/or/tor
add .exe files to gitignore
2010-02-25 23:02:02 +01:00
/src/or/tor.exe
Coverage support: build with --enable-coverage to have tests run with gcov If you pass the --enable-coverage flag on the command line, we build our testing binaries with appropriate options eo enable coverage testing. We also build a "tor-cov" binary that has coverage enabled, for integration tests. On recent OSX versions, test coverage only works with clang, not gcc. So we warn about that. Also add a contrib/coverage script to actually run gcov with the appropriate options to generate useful .gcov files. (Thanks to automake, the .o files will not have the names that gcov expects to find.) Also, remove generated gcda and gcno files on clean.
2013-07-09 18:37:11 +02:00
/src/or/tor-cov
/src/or/tor-cov.exe
Move testing code into new src/test directory.
2009-09-22 18:31:15 +02:00
/src/or/libtor.a
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
/src/or/libtor-testing.a
Add some MSVC stuff to gitignore
2012-05-14 18:35:10 +02:00
/src/or/libtor.lib
Move testing code into new src/test directory.
2009-09-22 18:31:15 +02:00
# /src/test
/src/test/Makefile
/src/test/Makefile.in
New src/test/bench.c to allow us to actually _run_ benchmark code Yes, the timing functions are suboptimal. Please improve!
2011-11-11 18:34:03 +01:00
/src/test/bench
/src/test/bench.exe
Move testing code into new src/test directory.
2009-09-22 18:31:15 +02:00
/src/test/test
Tests for backtrace.c These need to be a separate executable, since the point of backtrace.c is that it can crash and write stuff.
2013-07-30 03:56:31 +02:00
/src/test/test-bt-cl
Add a unit test for tor_spawn_background - Test sucessfully starting a process - Test failing to find the executable
2010-10-10 19:12:23 +02:00
/src/test/test-child
Add new ntor bits to gitignore
2012-12-08 06:57:19 +01:00
/src/test/test-ntor-cl
Add src/test/test{-child}.exe to gitignore. bug3626
2011-07-21 14:40:25 +02:00
/src/test/test.exe
Tests for backtrace.c These need to be a separate executable, since the point of backtrace.c is that it can crash and write stuff.
2013-07-30 03:56:31 +02:00
/src/test/test-bt-cl.exe
Add src/test/test{-child}.exe to gitignore. bug3626
2011-07-21 14:40:25 +02:00
/src/test/test-child.exe
Add new ntor bits to gitignore
2012-12-08 06:57:19 +01:00
/src/test/test-ntor-cl.exe
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# /src/tools/
/src/tools/tor-checkkey
/src/tools/tor-resolve
/src/tools/tor-gencert
add .exe files to gitignore
2010-02-25 23:02:02 +01:00
/src/tools/tor-checkkey.exe
/src/tools/tor-resolve.exe
/src/tools/tor-gencert.exe
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
/src/tools/Makefile
/src/tools/Makefile.in
First implementation of tor-fw-helper. tor-fw-helper is a command-line tool to wrap and abstract various firewall port-forwarding tools. This commit matches the state of Jacob's tor-fw-helper branch as of 23 September 2010. (commit msg by Nick)
2010-04-17 02:45:12 +02:00
# /src/tools/tor-fw-helper/
/src/tools/tor-fw-helper/tor-fw-helper
/src/tools/tor-fw-helper/tor-fw-helper.exe
/src/tools/tor-fw-helper/Makefile
/src/tools/tor-fw-helper/Makefile.in
Add an initial .gitignore to master
2009-04-29 15:19:18 +02:00
# /src/win32/
/src/win32/Makefile
/src/win32/Makefile.in
Reference in New Issue Copy Permalink