philippelh/bitchx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update docs to remove references to bitchx.com

Browse Source 
Thanks to cpet for the patch.
This commit is contained in:
Kevin Easton
2017-01-02 01:09:57 +11:00
parent 00ae33b67f
commit f8f6723b80
4 changed files with 17 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
bitchx-docs/7_Docs/About_BitchX
View File

@@ -20,24 +20,14 @@ maintained by Colten Edwards and a few others. EPIC is maintained by Jeremy
Nelson aka "hop". Alot of changes that appear within BitchX are backported Nelson aka "hop". Alot of changes that appear within BitchX are backported
to EPIC as I am a contributor to epic. to EPIC as I am a contributor to epic.
You can get a copy of the BitchX client via ftp from these mirrors: You can get a copy of the BitchX client from the official site:
Not all sites will be always up to date, but many of them try.
Site Directory Maintainer http://www.bitchx.org/
ftp.bitchx.com /pub/BitchX Mhacker/panasync
ftp.bitchx.org /pub/BitchX sideshow
If you want to mirror the BitchX client, please drop an email to Colten
Edwards (panasync@BitchX.com) telling him the host and directory where
we can count on you to keep a copy of the current version of the BitchX
client. The BitchX client takes about 1.2m, the help files take about 150k,
and from time to time there are other patches that range from 5k to 30k in
size.
A mailing list for all things related to BitchX exists. Send email to A mailing list for all things related to BitchX exists. Send email to
majordomo@lists.bitchx.com with the words "subscribe bitchx" in the body bitchx-devel@lists.sourceforge.net This list exists for bug reports,
(and nothing else!). This list exists for bug reports, discussion about and discussion about and requests for new features, and anything else that is
requests for new features, and anything else that has to do with BitchX. relevant to BitchX.
* BitchX is completely safe: There are no hidden trap doors. * BitchX is completely safe: There are no hidden trap doors.
We value your trust, and will not do anything to abuse it. We value your trust, and will not do anything to abuse it.

6
bitchx-docs/README_FIRST
View File

@@ -15,7 +15,7 @@ similar to the Unix manual system.
The implication of this, however, is that HELP can't work the same way The implication of this, however, is that HELP can't work the same way
as it used to. In order to read a helpfile now, its section number must as it used to. In order to read a helpfile now, its section number must
also be given. Thus, where one previously obtained help on WHOIS with also be given. Thus, where one previously obtained help on WHOIS with
"/help whois", one must now use "/help 2 whois". "/help whois", one must now use "/ehelp 2 whois".
Another change is the references to related topics in individual helpfiles, Another change is the references to related topics in individual helpfiles,
which is another similarity to Unix man pages. To better help users ease which is another similarity to Unix man pages. To better help users ease
@@ -23,8 +23,8 @@ into the new format, all topic references in the "See Also" sections will
include a Unix-ish section reference, such as "whois(2)". include a Unix-ish section reference, such as "whois(2)".
Also if your familar with a command and you find that it's not listed in Also if your familar with a command and you find that it's not listed in
here, please write a description of it and email it to here, please write a description of it and send it to
edwards@bitchx.dimension6.com. Your input here, might help someone else. bitchx-devel@lists.sourceforge.net. Your input here, might help someone else.
++ If you have not yet read "/ehelp 7 new_user", please do so now. ++ ++ If you have not yet read "/ehelp 7 new_user", please do so now. ++

22
doc/BitchX.devel
View File

@@ -8,35 +8,23 @@ $$$' $$$s $ .$$$$ `$$$$ d$$$$$$ $$$ $$$ .$' `$s.
$$$s. .s$$$$ $$ .$$$$$ `$$$$s. $$$$$$ $$$s $$$ s$ `$$$$s $$$s. .s$$$$ $$ .$$$$$ `$$$$s. $$$$$$ $$$s $$$ s$ `$$$$s
`$$$$Xavier$$$$$'s$$s $$$$$$s `S$$sss$$$$$'s$$$$$ s$$$ s$$s `$$$' `$$$$Xavier$$$$$'s$$s $$$$$$s `S$$sss$$$$$'s$$$$$ s$$$ s$$s `$$$'
Last Updated: Tue Apr 8 16:00:01 EDT 2003 Last Updated: Monday 2 January 01:04:16 AEDT 2017
BitchX is looking for coders to help maintain the client, add new features, BitchX is looking for coders to help maintain the client, add new features,
and fix any existing bugs. If you would be interested in helping, join #BitchX and fix any existing bugs. If you would be interested in helping, join #BitchX
on EFnet and let us know! on EFnet and let us know!
The BitchX Development Mailing List is available at bitchx-devel-request@lists.bitchx.org If your name is not listed below, and you think it should be, contact caf
Note, this is a closed mailing list and you will not be able to subscribe or post unless
you are approved for submissions. In general, only people that will be approved for
submission are listed below.
If your name is not listed below, and you think it should be, contact powuh
in #BitchX on EFnet. Anyone who actively finds bugs in BitchX, or who tests in #BitchX on EFnet. Anyone who actively finds bugs in BitchX, or who tests
new releases of BitchX is considered 'Quality Control' new releases of BitchX is considered 'Quality Control'
Current BitchX Team: Current BitchX Team:
panasync Original Author panasync Original Author
nuke Lead code maintainer
caf Lead code maintainer caf Lead code maintainer
sin FTP Site Maintainer, Quality Control
powuh Documentaion/FAQ Maintainer, Quality Control
Raistlin Mailing List Maintainer
sideshow bitchx.org domain name owner sideshow bitchx.org domain name owner
MHacker bitchx.com domain name owner
BlackJac Quality Control cpet Quality Control
|Rain| Quality Control sin Quality Control
void Quality Control Xavier Quality Control

2
doc/README.OS2
View File

@@ -26,7 +26,7 @@ IRCNICK = PMBXUser
HOSTNAME = mycomputer HOSTNAME = mycomputer
Scripts are located at scripts.bitchx.com. To install untar them into the Scripts are located in the scripts/ directory. To install untar them into the
HOME directory and /load them. Also try /load menu.bx for pull down HOME directory and /load them. Also try /load menu.bx for pull down
menus. If it is a clean installation and you don't have the HOME environment menus. If it is a clean installation and you don't have the HOME environment
variable set... it should load automatically. variable set... it should load automatically.