From: Johannes Sixt <j6t@kdbg.org>
To: Nikolaj Shurkaev <snnicky@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git log -z doesn't separate commits with NULs
Date: Thu, 23 Feb 2012 11:17:19 +0100 [thread overview]
Message-ID: <4F46122F.2040409@kdbg.org> (raw)
In-Reply-To: <4F46036F.3040406@gmail.com>
Am 23.02.2012 10:14, schrieb Nikolaj Shurkaev:
> I wanted to generate several files with some statistics using "git log
> -z" command.
> I did something like this:
> git log -z --patch HEAD~10..HEAD -- SomePathHere | xargs -0
> --max-chars=1000000 ~/1.sh
>
> If I put
> echo "started"
> into the file ~/1.sh I see that the file is called only once instead of
> multiple times.
That is because xargs calls the program with as many arguments as
possible, unless directed otherwise. Put this in the script:
echo "started $*"
and repeat. Then try this:
... | xargs -0 -n 1 ~/1.sh
-- Hannes
next prev parent reply other threads:[~2012-02-23 10:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 9:14 git log -z doesn't separate commits with NULs Nikolaj Shurkaev
2012-02-23 10:02 ` Luke Diamand
2012-02-23 10:27 ` Jeff King
2012-02-23 10:17 ` Johannes Sixt [this message]
2012-02-23 12:11 ` Nikolaj Shurkaev
2012-02-23 10:24 ` Jeff King
2012-02-23 12:17 ` Nikolaj Shurkaev
2012-02-23 13:15 ` Jakub Narebski
2012-02-23 13:48 ` Nikolaj Shurkaev
2012-02-23 19:34 ` Jeff King
2012-02-23 20:07 ` Junio C Hamano
2012-02-24 9:21 ` Nikolaj Shurkaev
2012-02-24 9:52 ` Jeff King
2012-02-24 20:03 ` Junio C Hamano
2012-02-24 20:46 ` Jeff King
2012-02-24 21:14 ` Junio C Hamano
2012-02-24 21:16 ` Jeff King
2012-03-03 13:41 ` Nikolaj Shurkaev
2012-02-24 22:11 ` Jakub Narebski
2012-02-24 22:27 ` Junio C Hamano
2012-02-23 10:35 ` Andreas Schwab
2012-02-23 12:19 ` Nikolaj Shurkaev
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=4F46122F.2040409@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=snnicky@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.