SliTaz Repositories

     1.1 --- a/README	Sun Jan 05 00:01:34 2014 +0100
     1.2 +++ b/README	Sun Jan 05 09:10:27 2014 +0000
     1.3 @@ -2,7 +2,7 @@
     1.4  ================================================================================
     1.5  
     1.6  
     1.7 -The SliTaz Project have setup and tried several bug trackers but they were never
     1.8 +The SliTaz Project has setup and tried several bug trackers but they were never
     1.9  adopted by the main developers. This is an attempt to change that by providing
    1.10  a radically simple tool well integrated with the SliTaz packages Cooker, Cookiso,
    1.11  Roadmap and other sites such as the wiki and forum.

     2.1 --- a/TODO	Sun Jan 05 00:01:34 2014 +0100
     2.2 +++ b/TODO	Sun Jan 05 09:10:27 2014 +0000
     2.3 @@ -4,6 +4,6 @@
     2.4  	* Hg integration by checking in commits if a bug was solved
     2.5  	  and then close it: hg commit -m "My msg [CLOSE=4]"
     2.6  	  Or full Hg integration ? Meaning the tracker itself under Hg and
     2.7 -	  each new bug or msg create a commit like in TinyCM ?
     2.8 +	  each new bug or msg creates a commit like in TinyCM ?
     2.9  	* If TinyCM is adopted and the SliTaz authentification system is
    2.10  	  approved: split auth code into /usr/lib/slitaz/libcgiauth.sh

     3.1 --- a/tazbug-box	Sun Jan 05 00:01:34 2014 +0100
     3.2 +++ b/tazbug-box	Sun Jan 05 09:10:27 2014 +0000
     3.3 @@ -1,6 +1,6 @@
     3.4  #!/bin/sh
     3.5  #
     3.6 -# SliTaz Bug GUI tool. All the account's parts may move to slitaz-account
     3.7 +# SliTaz Bug GUI tool. All the account parts may move to slitaz-account
     3.8  # if we use it for other sites and services so we use one centralized
     3.9  # SliTaz account.
    3.10  #

     4.1 --- a/web/bugs.cgi	Sun Jan 05 00:01:34 2014 +0100
     4.2 +++ b/web/bugs.cgi	Sun Jan 05 09:10:27 2014 +0000
     4.3 @@ -536,7 +536,7 @@
     4.4  		fi
     4.5  
     4.6  		if [  ! -f $AUTH_FILE ] ; then
     4.7 -			js_log "$AUTH_FILE (defined in \$AUTH_FILE) have not been found."
     4.8 +			js_log "$AUTH_FILE (defined in \$AUTH_FILE) has not been found."
     4.9  			js_redirection_to "$WEB_URL?login$IDLOC"
    4.10  		fi;
    4.11  
    4.12 @@ -549,10 +549,10 @@
    4.13  			mkdir -p $sessions
    4.14  			echo "$md5session" > $sessions/$user
    4.15  			js_set_cookie 'auth' "$user:$md5session"
    4.16 -			js_log "Login authentification have been executed & accepted :)"
    4.17 +			js_log "Login authentification has been executed & accepted :)"
    4.18  			js_redirection_to "$WEB_URL$IDLOC"
    4.19  		else
    4.20 -			js_log "Login authentification have been executed & refused"
    4.21 +			js_log "Login authentification has been executed & refused"
    4.22  			js_redirection_to "$WEB_URL?login&error$IDLOC"
    4.23  		fi
    4.24  		html_footer ;;

     5.1 --- a/web/plugins/dashboard/dashboard.cgi	Sun Jan 05 00:01:34 2014 +0100
     5.2 +++ b/web/plugins/dashboard/dashboard.cgi	Sun Jan 05 09:10:27 2014 +0000
     5.3 @@ -11,7 +11,7 @@
     5.4  		html_header
     5.5  		user_box
     5.6  		if ! admin_user; then
     5.7 -			gettext "You must be admin in to manage users."
     5.8 +			gettext "You must be admin to manage users."
     5.9  			exit 0
    5.10  		fi
    5.11  		users=$(ls -1 $PEOPLE | wc -l)

     6.1 --- a/web/plugins/skel/skel.cgi	Sun Jan 05 00:01:34 2014 +0100
     6.2 +++ b/web/plugins/skel/skel.cgi	Sun Jan 05 09:10:27 2014 +0000
     6.3 @@ -14,7 +14,7 @@
     6.4  	
     6.5  	# Say we use files in $DATA/skel, sort them by date and simply cat
     6.6  	# the files, this will create a simple blog :-) We may add post via
     6.7 -	# uploads or an HTML form.
     6.8 +	# uploads or a HTML form.
     6.9  	
    6.10  	html_footer
    6.11  	exit 0