git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chen WANG" <ellre923@gmail.com>
To: "'Jeff King'" <peff@peff.net>,
	"Chen Wang \(QA-CN\)" <chen_wang@trendmicro.com.cn>
Cc: <j.sixt@viscovery.net>, <git@vger.kernel.org>
Subject: RE: pretty format can't work on cron job
Date: Sat, 6 Nov 2010 12:42:07 +0800	[thread overview]
Message-ID: <01c101cb7d6c$fd053cf0$f70fb6d0$@com> (raw)
In-Reply-To: <20101105131444.GB11707@sigill.intra.peff.net>

> -----Original Message-----
> From: Jeff King [mailto:peff@peff.net]
> Sent: 2010年11月5日 21:15
> To: chen_wang@trendmicro.com.cn
> Cc: j.sixt@viscovery.net; git@vger.kernel.org; ellre923@gmail.com
> Subject: Re: pretty format can't work on cron job
> 
> On Fri, Nov 05, 2010 at 04:47:05PM +0800, chen_wang@trendmicro.com.cn
> wrote:
> 
> > > > But when I put that command on cron job, even I run “. /etc/profile” and
> “.
> > > ~/.bash_profile” first, I can’t get correct format of output.
> > > > -------------------------------------------------
> > > > Author: %aN <amit.shah@redhat.com>; Date: Wed Oct 20 13:45:43 2010
> > > +1030
> > > >  100.0% drivers/char/
> > > >  1 files changed, 14 insertions(+), 3 deletions(-)
> > > > -------------------------------------------------
> > >
> > > % has a special meaning in a crontab. See man 5 crontab.
> > >
> >
> > I warped this command in script and trigger script in crontab.
> > I think it's not the root cause, because %ae still works.
> 
> I notice that the only placeholder that is broken is %aN, which converts
> using the .mailmap file. Maybe something in your environment is
> preventing reading that file properly?
> 

$ ll .mailmap
-rw-r--r-- 1 wangchen club 4021 Oct 15 06:18 .mailmap

> Can you show us the exact script you're calling from your crontab file?
> I'm wondering if it's something to do with being in the same directory.
> 

Sure.
$ crontab -l
58 06 * * * /home/wangchen/kps_update
$ cat /home/wangchen/kps_update
#!/bin/bash
su wangchen -
. /etc/profile
. ~/.bash_profile
cd /home/wangchen/kps
git pull
make
cd /home/wangchen/linux-2.6
git pull
/home/wangchen/kps/kps_web/kps_do /home/wangchen/linux-2.6 /home/wangchen/kps
$ cat /home/wangchen/kps/kps_web/kps_do
#!/bin/sh
#check script parameters
if [ -r $1 -a -w $2 ]; then
        echo "begin to update kps_result"
        readonly LGP=$1
        KGP=$2
        KGP=${KGP%%/}
else
        echo "usage: $0 linux_kernel_source_dir kps_source_dir"
        exit 1
fi
cd $LGP
git log 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2.. -M --date=short --pretty=format:"Author: %aN <%ae>; Date: %ad" --shortstat --dirstat --no-merges >/tmp/ChangeLog-all

> -Peff

  reply	other threads:[~2010-11-06  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05  8:29 pretty format can't work on cron job chen_wang
2010-11-05  8:37 ` Johannes Sixt
2010-11-05  8:47   ` chen_wang
2010-11-05 13:14     ` Jeff King
2010-11-06  4:42       ` Chen WANG [this message]
2010-11-07 19:18         ` Thomas Rast
2010-11-08  2:30           ` Chen WANG

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='01c101cb7d6c$fd053cf0$f70fb6d0$@com' \
    --to=ellre923@gmail.com \
    --cc=chen_wang@trendmicro.com.cn \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=peff@peff.net \
    /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).