From: Jeff King <peff@peff.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Junio C Hamano <gitster@pobox.com>,
Anatol Pomozov <anatol.pomozov@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Make Git accept absolute path names for files within the work tree
Date: Thu, 6 Dec 2007 01:12:34 -0500 [thread overview]
Message-ID: <20071206061234.GC23309@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712041444090.13796@woody.linux-foundation.org>
On Tue, Dec 04, 2007 at 02:52:15PM -0800, Linus Torvalds wrote:
> IOW, that whole thing is simply a bug waiting to happen. The fact that it
> apparently *always* runs whether needed or not just seems to make it worse
> (ie if we already know our cwd, and the absolute path we have already has
> that as a prefix, just strip it off, don't try to do anything complex, and
> leave the complex and fragile cases for the odd-ball when the simple
> approach doesn't work)
Fair enough. Something like this then? It gets called only as a
last-ditch (though I think the 'return path' should simply be a die
-- what is the point of getting a pathspec that isn't in the repo?).
---
diff --git a/setup.c b/setup.c
index 4ee8024..fbb956e 100644
--- a/setup.c
+++ b/setup.c
@@ -5,13 +5,17 @@ static int inside_git_dir = -1;
static int inside_work_tree = -1;
static
-const char *strip_work_tree_path(const char *prefix, int len, const char *path)
+const char *strip_work_tree_path(const char *prefix, int len, const char *path,
+ int canonicalized)
{
const char *work_tree = get_git_work_tree();
int n = strlen(work_tree);
if (strncmp(path, work_tree, n))
- return path;
+ return canonicalized ?
+ path :
+ strip_work_tree_path(prefix, len,
+ xstrdup(make_absolute_path(path)), 1);
if (!prefix && !path[n])
return path + n;
@@ -58,7 +62,7 @@ const char *prefix_path(const char *prefix, int len, const char *path)
{
const char *orig = path;
if (is_absolute_path(path))
- path = strip_work_tree_path(prefix, len, path);
+ path = strip_work_tree_path(prefix, len, path, 0);
for (;;) {
char c;
next prev parent reply other threads:[~2007-12-06 6:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 0:52 Incorrect git-blame result if I use full path to file Anatol Pomozov
2007-12-03 2:19 ` Junio C Hamano
2007-12-03 2:28 ` Jeff King
2007-12-03 17:26 ` Linus Torvalds
2007-12-03 18:09 ` Johannes Schindelin
2007-12-03 18:13 ` Linus Torvalds
2007-12-03 18:19 ` Linus Torvalds
2007-12-03 2:27 ` Jeff King
2007-12-03 2:40 ` Junio C Hamano
2007-12-03 2:49 ` Jeff King
2007-12-03 6:55 ` Robin Rosenberg
2007-12-03 20:53 ` [PATCH] Make Git accept absolute path names for files within the work tree Robin Rosenberg
2007-12-03 23:03 ` Junio C Hamano
2007-12-04 1:43 ` Jeff King
2007-12-04 2:17 ` Johannes Schindelin
2007-12-04 6:42 ` Robin Rosenberg
2007-12-04 11:50 ` Johannes Schindelin
2007-12-04 15:59 ` Linus Torvalds
2007-12-04 22:08 ` Jeff King
2007-12-04 22:52 ` Linus Torvalds
2007-12-06 6:12 ` Jeff King [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-26 23:18 Robin Rosenberg
2007-11-27 0:24 ` Junio C Hamano
2007-11-27 23:20 ` Robin Rosenberg
2007-11-27 23:24 ` Robin Rosenberg
2007-11-28 8:43 ` Junio C Hamano
2007-11-29 1:15 ` Robin Rosenberg
2007-11-29 2:05 ` Junio C Hamano
2007-11-29 0:37 ` Junio C Hamano
2007-11-27 8:45 ` Johannes Sixt
2007-11-27 23:14 ` 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=20071206061234.GC23309@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=anatol.pomozov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.com \
--cc=torvalds@linux-foundation.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).