Changes between Version 36 and Version 37 of WikiStart


Ignore:
Timestamp:
07/08/09 21:17:08 (15 years ago)
Author:
zaytsev
Comment:

Even more fixes

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v36 v37  
    2424=== mc-devel (at) gnome (dot) org === 
    2525Mailing list for the development-related discussions: 
    26  * Click here to [http://mail.gnome.org/mailman/listinfo/mc-devel Subscribe]; 
    27  * Click here to [http://mail.gnome.org/archives/mc-devel/ read the Archives]. 
     26 * Click here to [http://mail.gnome.org/mailman/listinfo/mc-devel subscribe]; 
     27 * Click here to [http://mail.gnome.org/archives/mc-devel/ read the archives]. 
    2828 
    2929=== mc-commits (at) googlegroups (dot) com === 
    3030Mailing list reserved for the applied commits into master/mc-4.6 branches only (suitable for use as RSS): 
    31  * Click here to [http://groups.google.com/group/mc-commits/subscribe Subscribe]; 
    32  * Click here to [http://groups.google.com/group/mc-commits read the Archives]. 
     31 * Click here to [http://groups.google.com/group/mc-commits/subscribe subscribe]; 
     32 * Click here to [http://groups.google.com/group/mc-commits read the archives]. 
    3333 
    3434=== mc-bugs (at) googlegroups (dot) com === 
    3535Mailing list reserved for the ticket and comment notifications only (suitable for use as RSS): 
    36  * Click here to [http://groups.google.com/group/mc-bugs/subscribe Subscribe]; 
    37  * Click here to [http://groups.google.com/group/mc-bugs read the Archives]. 
     36 * Click here to [http://groups.google.com/group/mc-bugs/subscribe subscribe]; 
     37 * Click here to [http://groups.google.com/group/mc-bugs read the archives]. 
    3838 
    3939== Mailing list for the users == 
    4040=== mc (at) gnome (dot) org === 
    41  * Click here to [http://mail.gnome.org/mailman/listinfo/mc Subscribe]; 
    42  * Click here to [http://mail.gnome.org/archives/mc/ read the Archives]. 
     41 * Click here to [http://mail.gnome.org/mailman/listinfo/mc subscribe]; 
     42 * Click here to [http://mail.gnome.org/archives/mc/ read the archives]. 
    4343 
    4444== Other resources == 
    … …  
    4646This is your English-speaking jabber room. 
    4747 
    48 == Downloading == 
    49 A list of the lastest releases can be found [http://www.midnight-commander.org/downloads here]. If you are interested in developing please have also a look on our git: 
    50 In order to get a checkout of the git use this: 
     48== Download == 
     49A list of the latest releases is available [http://www.midnight-commander.org/downloads here]. If you are interested in helping with the development please also have a look at our Git repository. In order to check out the repository tree use the following commands: 
    5150 * git clone git://midnight-commander.org/git/mc.git 
    52  * git clone http://git.midnight-commander.org/mc.git (For those who are behind a firewall) 
     51 * git clone http://git.midnight-commander.org/mc.git (for those who are behind a firewall) 
    5352 
    54 We also have an autosyncing git mirror at [[http://repo.or.cz/w/midnight-commander.git/ repo.or.cz]] 
    55 As it uses gitweb at Web UI - it can provide information unavailable via trac browse plugin.  
     53We also have an autosyncing Git mirror at [[http://repo.or.cz/w/midnight-commander.git/ repo.or.cz]]. It uses gitweb as the web-interface to Git and can therefore provide some information normally unavailable via Trac Git browser plug-in: 
    5654 * git clone git://repo.or.cz/midnight-commander.git 
    5755 * git clone http://repo.or.cz/r/midnight-commander.git 
    5856 
    59 == Contributing == 
    60 You are interested in mc and would like to improve it? Cool! Feel free to post your patches to the tickets and review patches there. If you do this on a regular basis we'll ask you if you maybe want to become a dev.  
    61 However when you work with the ticket system please have a look on our WorkingGuideLines, so that your work is noticed by us.  
     57== Contribute == 
     58You are interested in mc and would like to improve it? Cool! Feel free to report bugs, attach your patches to the tickets and review the patches, that are already in there. If you are going to do this on a regular basis, we'll ask you if you'd like to join us. However, please search before reporting your issues to reduce the amount of work, needed to close duplicate reports. Please also have a look at our WorkingGuideLines before you actually start messing with the ticket system. 
    6259 
    63 If you are unfamiliar with git, you can also have a short view on our GitGuideLines where the workflow with git is described quite practical.  
     60If you are not familiar with git, you might find our GitGuideLines enlightening. It's a short overview of the practical side of our workflow with Git.