public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3873] maintainer-scripts: fix superfluous 'sh' for Python script Date: Thu, 10 Nov 2022 05:39:56 +0000 (GMT) [thread overview] Message-ID: <20221110053956.668133858438@sourceware.org> (raw) https://gcc.gnu.org/g:9072763f4f17e600a980ff510b2baf8ad8ada1b5 commit r13-3873-g9072763f4f17e600a980ff510b2baf8ad8ada1b5 Author: Martin Liska <mliska@suse.cz> Date: Thu Nov 10 06:37:32 2022 +0100 maintainer-scripts: fix superfluous 'sh' for Python script maintainer-scripts/ChangeLog: * crontab: Fix superfluous 'sh' for Python script. Diff: --- maintainer-scripts/crontab | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maintainer-scripts/crontab b/maintainer-scripts/crontab index 09e33c0095f..0fd885ea759 100644 --- a/maintainer-scripts/crontab +++ b/maintainer-scripts/crontab @@ -1,5 +1,5 @@ 16 0 * * * sh /home/gccadmin/scripts/update_version_git -50 0 * * * sh /home/gccadmin/venv/bin/python3 /home/gccadmin/scripts/update_web_docs_git.py /www/gcc/htdocs/onlinedocs/ --sphinx-build=/home/gccadmin/venv/bin/sphinx-build +50 0 * * * /home/gccadmin/venv/bin/python3 /home/gccadmin/scripts/update_web_docs_git.py /www/gcc/htdocs/onlinedocs/ --sphinx-build=/home/gccadmin/venv/bin/sphinx-build 55 0 * * * sh /home/gccadmin/scripts/update_web_docs_libstdcxx_git 32 22 * * 4 sh /home/gccadmin/scripts/gcc_release -s 10:releases/gcc-10 -l -d /sourceware/snapshot-tmp/gcc all 32 22 * * 5 sh /home/gccadmin/scripts/gcc_release -s 11:releases/gcc-11 -l -d /sourceware/snapshot-tmp/gcc all
reply other threads:[~2022-11-10 5:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20221110053956.668133858438@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).