From: Johannes Sixt <j.sixt@viscovery.net>
To: "SZEDER Gábor" <szeder@fzi.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"SZEDER Gábor" <szeder@ira.uka.de>,
git@vger.kernel.org
Subject: Re: [RFC PATCH] Fix gitdir detection when in subdir of gitdir
Date: Mon, 19 Jan 2009 08:17:17 +0100 [thread overview]
Message-ID: <497428FD.7050301@viscovery.net> (raw)
In-Reply-To: <20090119020311.GA8753@neumann>
SZEDER Gábor schrieb:
> if (is_git_directory(".")) {
> + char gd_rel_path[PATH_MAX];
> inside_git_dir = 1;
> if (!work_tree_env)
> inside_work_tree = 0;
> - setenv(GIT_DIR_ENVIRONMENT, ".", 1);
> + if (cdup_count) {
> + char *p = gd_rel_path;
> + while (cdup_count-- > 1) {
> + *p++ = '.'; *p++ = '.'; *p++ = '/';
> + }
> + *p++ = '.'; *p++ = '.';
> + *p = '\0';
> + } else {
> + gd_rel_path[0] = '.';
> + gd_rel_path[1] = '\0';
> + }
> + setenv(GIT_DIR_ENVIRONMENT, gd_rel_path, 1);
> check_repository_format_gently(nongit_ok);
> return NULL;
> }
This does not make sense because you don't chdir back to where you
started, so the relative path would be incorrect.
I have the feeling that it is not worth to support this particular
use-case with so many lines of code.
-- Hannes
next prev parent reply other threads:[~2009-01-19 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 15:37 [RFC PATCH] Fix gitdir detection when in subdir of gitdir SZEDER Gábor
2009-01-16 16:29 ` Johannes Schindelin
2009-01-16 16:47 ` Johannes Sixt
2009-01-16 16:50 ` Johannes Sixt
2009-01-16 17:23 ` SZEDER Gábor
2009-01-16 18:07 ` Junio C Hamano
2009-01-16 20:55 ` Johannes Schindelin
2009-01-18 21:27 ` Junio C Hamano
2009-01-19 2:03 ` SZEDER Gábor
2009-01-19 3:15 ` Junio C Hamano
2009-01-19 7:17 ` Johannes Sixt [this message]
2009-01-19 2:08 ` [PATCH] t1500: extend with tests of 'git rev-parse --git-dir' SZEDER Gábor
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=497428FD.7050301@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@fzi.de \
--cc=szeder@ira.uka.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.