git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: [JGIT PATCH 02/10] Expose the raw path for the current entry of a TreeWalk
Date: Thu, 22 Jan 2009 15:28:02 -0800	[thread overview]
Message-ID: <1232666890-23488-3-git-send-email-spearce@spearce.org> (raw)
In-Reply-To: <1232666890-23488-2-git-send-email-spearce@spearce.org>

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.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
 .../src/org/spearce/jgit/treewalk/TreeWalk.java    |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/org.spearce.jgit/src/org/spearce/jgit/treewalk/TreeWalk.java b/org.spearce.jgit/src/org/spearce/jgit/treewalk/TreeWalk.java
index 414587c..22040e3 100644
--- a/org.spearce.jgit/src/org/spearce/jgit/treewalk/TreeWalk.java
+++ b/org.spearce.jgit/src/org/spearce/jgit/treewalk/TreeWalk.java
@@ -663,6 +663,21 @@ public String getPathString() {
 	}
 
 	/**
+	 * Get the current entry's complete path as a UTF-8 byte array.
+	 * 
+	 * @return complete path of the current entry, from the root of the
+	 *         repository. If the current entry is in a subtree there will be at
+	 *         least one '/' in the returned string.
+	 */
+	public byte[] getRawPath() {
+		final AbstractTreeIterator t = currentHead;
+		final int n = t.pathLen;
+		final byte[] r = new byte[n];
+		System.arraycopy(t.path, 0, r, 0, n);
+		return r;
+	}
+
+	/**
 	 * Test if the supplied path matches the current entry's path.
 	 * <p>
 	 * This method tests that the supplied path is exactly equal to the current
-- 
1.6.1.399.g0d272

  reply	other threads:[~2009-01-22 23:29 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   ` Shawn O. Pearce [this message]
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     ` [JGIT PATCH 02/10] Expose the raw path for the current entry of a TreeWalk Robin Rosenberg

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=1232666890-23488-3-git-send-email-spearce@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg@dewire.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 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).