From: Alex Riesen <raa.lkml@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Joey Hess <joey@kitenet.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: git log and utf-u in filenames
Date: Fri, 26 Sep 2008 08:33:11 +0200 [thread overview]
Message-ID: <20080926063311.GA4939@blimp.localhost> (raw)
In-Reply-To: <m3fxnn3ji6.fsf@localhost.localdomain>
Jakub Narebski, Fri, Sep 26, 2008 01:15:58 +0200:
>
> Well, in gitweb we could use '-z' option for git-diff-tree and git-ls-tree,
> but it has its disadvantages, like having to do actual parsing record after
> record instead of simplys splitting outout on end of line ("\n") characters.
>
How about simply splitting output on end of line ("\0" NUL) characters?
The "\n" NL you refer to is just as EOR as NUL.
next prev parent reply other threads:[~2008-09-26 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 21:50 git log and utf-u in filenames Joey Hess
2008-09-25 22:43 ` Joey Hess
2008-09-25 23:15 ` Jakub Narebski
2008-09-26 6:33 ` Alex Riesen [this message]
2008-09-26 7:31 ` Jakub Narebski
2008-09-26 13:49 ` Alex Riesen
2008-09-27 8:37 ` Jakub Narebski
2008-09-25 23:11 ` Jakub Narebski
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=20080926063311.GA4939@blimp.localhost \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=joey@kitenet.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).