git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Hord <hordp@cisco.com>
To: git@vger.kernel.org
Cc: phil.hord@gmail.com, Phil Hord <hordp@cisco.com>
Subject: [RFC/PATCH] Fix path prefixing in grep_object
Date: Sat, 24 Aug 2013 21:35:58 -0400	[thread overview]
Message-ID: <1377394558-371-1-git-send-email-hordp@cisco.com> (raw)

When the pathspec given to grep includes a tree name, the full
name of matched files is assembled using colon as a separator.
If the pathspec includes a tree name, it should use a slash
instead.

Check if the pathspec already names a tree and ref (including
a colon) and use a slash if so.
---

I'm not sure about the detection I used here.  It works, but it is
not terribly robust.  Is there a better way to handle this?  Maybe
something like 'prefix_pathspec(name,"");'.

 builtin/grep.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/builtin/grep.c b/builtin/grep.c
index 03bc442..d0deae4 100644
--- a/builtin/grep.c
+++ b/builtin/grep.c
@@ -480,8 +480,9 @@ static int grep_object(struct grep_opt *opt, const struct pathspec *pathspec,
 		len = name ? strlen(name) : 0;
 		strbuf_init(&base, PATH_MAX + len + 1);
 		if (len) {
+			int has_colon = !!strchr(name,':');
 			strbuf_add(&base, name, len);
-			strbuf_addch(&base, ':');
+			strbuf_addch(&base, has_colon?'/':':');
 		}
 		init_tree_desc(&tree, data, size);
 		hit = grep_tree(opt, pathspec, &tree, &base, base.len,
-- 
1.8.4.557.g34b3a2e

             reply	other threads:[~2013-08-25  1:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25  1:35 Phil Hord [this message]
2013-08-25  2:07 ` [RFC/PATCH] Fix path prefixing in grep_object Phil Hord
2013-08-25  3:35   ` Junio C Hamano
2013-08-25  4:23     ` Jonathan Nieder
2013-08-25  5:25       ` Junio C Hamano
2013-08-26  7:14         ` Junio C Hamano
2013-08-26 11:44           ` Phil Hord
2013-08-26 16:23             ` Junio C Hamano
2013-08-26 16:49               ` Phil Hord
2013-08-26 17:07                 ` Phil Hord
2013-08-26 17:26                 ` Junio C Hamano
2013-08-26 17:45                   ` Phil Hord
2013-08-27  4:07                   ` Junio C Hamano
2013-08-27 11:54                     ` Phil Hord
2013-08-26 17:03               ` Junio C Hamano
2013-08-26 17:19                 ` Phil Hord
2013-08-25  4:41 ` Jeff King
2013-08-25  5:41   ` Jonathan Nieder
2013-08-25  5:54     ` Jeff King

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=1377394558-371-1-git-send-email-hordp@cisco.com \
    --to=hordp@cisco.com \
    --cc=git@vger.kernel.org \
    --cc=phil.hord@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 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).