git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Lichtenheld <frank@lichtenheld.de>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: gitster@pobox.com, Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH RESEND] Git.pm: Always set Repository to absolute path if autodetecting
Date: Wed, 27 May 2009 12:54:55 +0200	[thread overview]
Message-ID: <20090527105454.GW17706@mail-vs.djpig.de> (raw)
In-Reply-To: <4A1A49C0.7040102@viscovery.net>

On Mon, May 25, 2009 at 09:33:20AM +0200, Johannes Sixt wrote:
> Frank Lichtenheld schrieb:
> > From: Frank Lichtenheld <flichtenheld@astaro.com>
> > 
> > So far we only set it to absolute paths in some cases which lead
> > to problems like wc_chdir not working.
> > 
> > Signed-off-by: Frank Lichtenheld <flichtenheld@astaro.com>
> > ---
> >  perl/Git.pm     |    2 +-
> >  t/t9700/test.pl |   10 ++--------
> >  2 files changed, 3 insertions(+), 9 deletions(-)
> > 
> > Resent unchanged. There was one comment which I've reponded too and
> > argued that it didn't apply and there was no further objections.
> > 
> > diff --git a/perl/Git.pm b/perl/Git.pm
> > index 4313db7..e8df55d 100644
> > --- a/perl/Git.pm
> > +++ b/perl/Git.pm
> > @@ -185,7 +185,7 @@ sub repository {
> >  
> >  		if ($dir) {
> >  			$dir =~ m#^/# or $dir = $opts{Directory} . '/' . $dir;
> > -			$opts{Repository} = $dir;
> > +			$opts{Repository} = abs_path($dir);
> 
> Unfortunately, this change breaks MinGW git because the absolute path that
> this produces is MSYS-style /c/path/to/repo, but git does not understand
> this; it should be c:/path/to/repo. This value is ultimately assigned to
> GIT_DIR, but the path name mangling that usually happens when an MSYS
> program (like perl) spawns a non-MSYS program (like git) does not happen.
> 
> Your commit message is quite vague about the problems that you have seen.
> I vote to revert this change.

Note that abs_path is already used twice in the same function. Why are those
usages not problematic? I would be happy to work with you on finding a patch
that doesn't break, but I have to admit that I have no idea of the
Windows<->Perl<->git interactions.

As for the problems, a part of the public API of the module simply doesn't work
(i.e. wc_chdir) which I fixed. If we can't fix it we should at least not pretend
that it works.

Gruesse,
-- 
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/

  reply	other threads:[~2009-05-27 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 13:41 [PATCH RESEND] Git.pm: Set GIT_WORK_TREE if we set GIT_DIR Frank Lichtenheld
2009-05-07 13:41 ` [PATCH RESEND] Git.pm: Always set Repository to absolute path if autodetecting Frank Lichtenheld
2009-05-25  7:33   ` Johannes Sixt
2009-05-27 10:54     ` Frank Lichtenheld [this message]
2009-05-27 11:16       ` Johannes Sixt
2009-05-27 13:46         ` Frank Lichtenheld
2009-05-07 19:40 ` [PATCH RESEND] Git.pm: Set GIT_WORK_TREE if we set GIT_DIR Petr Baudis

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=20090527105454.GW17706@mail-vs.djpig.de \
    --to=frank@lichtenheld.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    --cc=pasky@suse.cz \
    /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).