[Qa-jenkins-scm] [jenkins.debian.net] 01/01: README: clarify to log into alioth via ssh

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit 1e44dc0cc5eca0c42701719ff9ca53ec2f2527da
Author: josch <j.schauer at email.de>
Date:   Wed Jun 17 18:59:41 2015 +0200

    README: clarify to log into alioth via ssh
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index 7b11172..ec72e86 100644
--- a/README
+++ b/README
@@ -161,7 +161,7 @@ Installation tests inside chroot environments.
 * The jenkins job overview at https://jenkins.debian.net/view/reproducible/ probably makes it clearer how the job scheduling works in practice.
 
 * If you are in the reproducible team you can reschedule packages by yourself:
-** log into alioth.debian.org, in the team home (/home/groups/reproducible/) there is a reschedule.sh script you can call. Use the --help switch to get the online help.
+** log into alioth.debian.org via ssh, in the team home (/home/groups/reproducible/) there is a reschedule.sh script you can call. Use the --help switch to get the online help.
 ** The team IRC channel will get a notification both when the scheduling is done and once the build finishes.
 
 * If you are not in the reproducible team or if you want to reschedule big sets of packages please ask for a manual rescheduling in the '#debian-reproducible' IRC channel on OFTC. Those with shell access to jenkins can bypass the limitations imposed to remote calls (and e.g. schedule a lot of packages (remotes are limited at 50 per day) without notifications at the end).

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git