From: Johannes Schneider <mailings@cedarsoft.com>
To: git <git@vger.kernel.org>
Subject: Re: [OT?] Executing Git from bash script invoked by cron
Date: Sat, 03 Jul 2010 19:19:51 +0200 [thread overview]
Message-ID: <4C2F7137.6020209@cedarsoft.com> (raw)
In-Reply-To: <1277759597-sup-9397@nixos>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/28/2010 11:17 PM, Marc Weber wrote:
> sh -c 'your quoted command &> /tmp/logfile'
>
> b) if this still does not work use strace:
That is it. Thanks.
Of course, git writes to stderr. And I did not redirect it properly.
I don't understand the details, but this line is working now:
sh -c 'myscript' >> logfile 2> err
The problem - by the way - is related to ssh authentification...
But that is another issue...
But here comes my question: Obviously all output created by git push is
written to stderr. I'd expected that most of the content will end up in
stdout.
But I am sure there is a good reason for it - so I just accept it ;-)
Thanks,
Johannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJML3E0AAoJEAytD9R7Qv6dZ5cIANpYYu5isncB3LcLaQgURQmP
esxkrtAVrcghItv+KkSts+qb8IBlEmA1mkzMYpmgVn6M/CQxh3atlaDsTbNtznAA
eZVJwXqQwoPlJS8ZvoDcSdldcL5Nmi+nyJgg408y5j3GB4AEt8IihxYVW7Xs0pFQ
GdBOSjV/TK1PEjcP7dNYJ9MSdUFA6Z7GrywRKQwlRZ4C611wCBpEoAeD0S1vcJcl
B78DTIqB+P3VF+mLW3u2LRXUdp3+tM2uutGR7DkG6GVomHJkwb5zAGXU4AmwHt2L
OdDwPAAZ5OzAgfyqLZ4YrOMv9Pg8sOjj+YLfljLUIXB/muJPACqNljv+liCmrac=
=X2Lj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-03 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 21:00 [OT?] Executing Git from bash script invoked by cron Johannes Schneider
2010-06-28 21:05 ` Sverre Rabbelier
2010-06-28 21:17 ` Marc Weber
2010-06-28 21:22 ` Sverre Rabbelier
2010-07-03 17:19 ` Johannes Schneider [this message]
2010-06-28 21:43 ` Ramkumar Ramachandra
2010-06-29 6:24 ` Matthieu Moy
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=4C2F7137.6020209@cedarsoft.com \
--to=mailings@cedarsoft.com \
--cc=git@vger.kernel.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: link
Be 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 NNTP newsgroup(s).