From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [JGIT PATCH 02/10] Expose the raw path for the current entry of a TreeWalk
Date: Fri, 23 Jan 2009 22:42:14 +0100 [thread overview]
Message-ID: <200901232242.15073.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <1232666890-23488-3-git-send-email-spearce@spearce.org>
fredag 23 januari 2009 00:28:02 skrev Shawn O. Pearce:
> Copying the path byte array (keeping it encoded in UTF-8) is quicker
> than converting to String and then back again to UTF-8 when creating
> a DirCacheEntry for the current position in a TreeWalk.
[...]
> + * Get the current entry's complete path as a UTF-8 byte array.
/Hopefully/ UTF-8. It is often a legacy encoding, like ISO-8859-X, CP12xx
etc. I'll come up with something less specific that just UTF-8.
-- robin
prev parent reply other threads:[~2009-01-23 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 23:28 [JGIT PATCH 00/10] Merge API v2 Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 01/10] Fix TreeWalk.idEqual when both trees are missing the path Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 02/10] Expose the raw path for the current entry of a TreeWalk Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 03/10] Expose DirCacheEntry.getFileMode as a utility function Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 04/10] Add writeTree support to DirCache Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 05/10] Allow a DirCache to be created with no backing store file Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 06/10] Allow CanonicalTreeParsers to be created with a UTF-8 path prefix Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 07/10] Recursively load an entire tree into a DirCacheBuilder Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 08/10] Allow DirCacheEntry instances to be created with stage > 0 Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 09/10] Define a basic merge API, and a two-way tree merge strategy Shawn O. Pearce
2009-01-22 23:28 ` [JGIT PATCH 10/10] Add a few simple merge test cases Shawn O. Pearce
2009-01-23 21:42 ` Robin Rosenberg [this message]
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=200901232242.15073.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).