From: Clemens Buchacher Date: Sat, 05 Jun 2010 08:04:20 GMT Subject: [PATCH] setup: document prefix Message-ID: <20100605080420.GA1151@localhost> In-Reply-To: <20100604075034.GB5117@localhost> Signed-off-by: Clemens Buchacher --- On Fri, Jun 04, 2010 at 09:50:34AM +0200, Clemens Buchacher wrote: > > By the way, I noticed that we rely on the fact that a non-empty > prefix ends with '/'. Is that ok? I checked and the prefix does always end in a slash currently, but this guarantee is well hidden in the code. I would feel more at ease to continue relying on this with the comment below. Regards, Clemens setup.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/setup.c b/setup.c index 5716d90..0e4cfe6 100644 --- a/setup.c +++ b/setup.c @@ -519,6 +519,12 @@ int check_repository_format(void) return check_repository_format_gently(NULL); } +/* + * Returns the "prefix", a path to the current working directory + * relative to the work tree root, or NULL, if the current working + * directory is not a strict subdirectory of the work tree root. The + * prefix always ends with a '/' character. + */ const char *setup_git_directory(void) { const char *retval = setup_git_directory_gently(NULL); -- 1.7.1.2.ga1f6e