1
0

GIT.txt 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465
  1. ngIRCd - Next Generation IRC Server
  2. http://ngircd.barton.de/
  3. (c)2001-2011 Alexander Barton and Contributors.
  4. ngIRCd is free software and published under the
  5. terms of the GNU General Public License.
  6. -- GIT.txt --
  7. The source code of ngIRCd is maintained using GIT, an distributed version
  8. control system. Homepage including documentation: <http://git-scm.com/>.
  9. I. Viewing the source code online
  10. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  11. The ngIRCd "GITweb" interface allows you to browse the GIT repository and
  12. to see all individual files, tags, branches, commits etc.:
  13. <http://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git>
  14. II. Getting the source code
  15. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  16. To access (copy, clone) the source tree repository anonymously, run:
  17. $ git clone git://ngircd.barton.de/ngircd.git
  18. Thereby a new folder "ngircd" will be created containing all the individual
  19. source files.
  20. The newly created directory ("ngircd") is the "working directory", all
  21. GIT commands will be executed from within this directory in the future.
  22. Please note: When checking out a fresh copy of ngIRCd using GIT, the
  23. configure script doesn't exist; you have to run the autogen.sh shell script
  24. (which is included in the source tree) to generate it. This requires you to
  25. have GNU automake and GNU autoconf installed on your system. Please see the
  26. file INSTALL for details!
  27. To update the local GIT repository:
  28. $ git pull
  29. This retrieves all changes and merges them into the current branch.
  30. III. Contributing
  31. ~~~~~~~~~~~~~~~~~
  32. Patches should be sent to the ngircd mailing list. List homepage:
  33. http://arthur.barton.de/mailman/listinfo/ngircd-ml
  34. If you do not want to send them to the list, you can also mail them
  35. to Alex Barton, <alex@barton.de>.
  36. IV. Write Access
  37. ~~~~~~~~~~~~~~~~
  38. If you want to contribute a couple of patches and write access to the GIT
  39. repository would be handy, please contact Alex Barton, <alex@barton.de>.