From f21a8fef149e141113e29757246764278161b20f Mon Sep 17 00:00:00 2001 From: Christian Berendt Date: Thu, 28 Apr 2016 16:09:01 -0500 Subject: [PATCH] Remove leading whitespaces from the Gerrit welcome message Change-Id: I02f02b361ded18d21013c2d8c58986340a6e5dfb --- jeepyb/cmd/welcome_message.py | 38 +++++++++++++++++------------------ 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/jeepyb/cmd/welcome_message.py b/jeepyb/cmd/welcome_message.py index 096832d..80d0a02 100644 --- a/jeepyb/cmd/welcome_message.py +++ b/jeepyb/cmd/welcome_message.py @@ -71,29 +71,29 @@ def post_message(commit, gerrit_user, gerrit_ssh_key, message_file): default_text = """Thank you for your first contribution to OpenStack. - Your patch will now be tested automatically by OpenStack testing frameworks - and once the automatic tests pass, it will be reviewed by other friendly - developers. They will give you feedback and may require you to refine it. +Your patch will now be tested automatically by OpenStack testing frameworks +and once the automatic tests pass, it will be reviewed by other friendly +developers. They will give you feedback and may require you to refine it. - People seldom get their patch approved on the first try, so don't be - concerned if requested to make corrections. Feel free to modify your patch - and resubmit a new change-set. +People seldom get their patch approved on the first try, so don't be +concerned if requested to make corrections. Feel free to modify your patch +and resubmit a new change-set. - Patches usually take 3 to 7 days to be reviewed so be patient and be - available on IRC to ask and answer questions about your work. Also it - takes generally at least a couple of weeks for cores to get around to - reviewing code. The more you participate in the community the more - rewarding it is for you. You may also notice that the more you get to know - people and get to be known, the faster your patches will be reviewed and - eventually approved. Get to know others and become known by doing code - reviews: anybody can do it, and it's a great way to learn the code base. +Patches usually take 3 to 7 days to be reviewed so be patient and be +available on IRC to ask and answer questions about your work. Also it +takes generally at least a couple of weeks for cores to get around to +reviewing code. The more you participate in the community the more +rewarding it is for you. You may also notice that the more you get to know +people and get to be known, the faster your patches will be reviewed and +eventually approved. Get to know others and become known by doing code +reviews: anybody can do it, and it's a great way to learn the code base. - Thanks again for supporting OpenStack, we look forward to working with you. +Thanks again for supporting OpenStack, we look forward to working with you. - IRC: https://wiki.openstack.org/wiki/IRC - Workflow: http://docs.openstack.org/infra/manual/developers.html - Commit Messages: https://wiki.openstack.org/wiki/GitCommitMessages - """ +IRC: https://wiki.openstack.org/wiki/IRC +Workflow: http://docs.openstack.org/infra/manual/developers.html +Commit Messages: https://wiki.openstack.org/wiki/GitCommitMessages +""" if message_file: try: