git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Scott R Parish <srp@srparish.net>, git@vger.kernel.org
Subject: Re: [PATCH] use only the PATH for exec'ing git commands
Date: Tue, 23 Oct 2007 00:34:27 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710230026380.25221@racer.site> (raw)
In-Reply-To: <20071022224015.GG23714@steel.home>

Hi,

On Tue, 23 Oct 2007, Alex Riesen wrote:

> Scott R Parish, Tue, Oct 23, 2007 00:12:02 +0200:
> > > Alex Riesen, Mon, Oct 22, 2007 12:01
> > > Scott R Parish, Mon, Oct 22, 2007 19:01:48 +0200:
> > > > +                strbuf_addch(out, ':');
> > >
> > > Shouldn't it break MingW32 native port?
> > 
> > What can i do here to better accommodate MingW32? You're right, just 
> > because the original code did it this way isn't a good excuse for me 
> > not to do it better.
> 
> someone here mentioned "higher abstractions".

That someone may well have mentioned that term, but what he meant was 
special case those code paths which have to be treated differently for 
Windows, and Windows alone.

(Yeah, I know, a response to that was that Nokia phones have drive 
letters, too, but that was an invalid objection to that particular 
statement, since Nokia phones expect the full path at any time, so I did 
not even bother answering to that mail.  Well, in a way, I guess I just 
did.)

All this boils down to adding code dedicated to Windows.  And I am a huge 
fan of the principle that you should cross bridges when you get to them, 
and not before (i.e. avoid over-engineering).

So my vote is: get it in as-is, us msysGit lot will cope with it in one 
way or another.  (We already have at least one other place where ":" is 
used, which we have to cope with, in shell.c:do_cvs_command().)

Ciao,
Dscho

  reply	other threads:[~2007-10-22 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 22:12 [PATCH] use only the PATH for exec'ing git commands Scott R Parish
2007-10-22 22:40 ` Alex Riesen
2007-10-22 23:34   ` Johannes Schindelin [this message]
2007-10-23  6:14 ` Johannes Sixt
  -- strict thread matches above, loose matches on Subject: below --
2007-10-22 19:59 Scott R Parish
2007-10-22 19:59 Scott R Parish
2007-10-22 20:57 ` Alex Riesen
2007-10-22 17:01 Scott R Parish
2007-10-22 17:44 ` Johannes Schindelin
2007-10-22 19:01 ` Alex Riesen
2007-10-22 19:25   ` Eric Merritt

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=Pine.LNX.4.64.0710230026380.25221@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    --cc=srp@srparish.net \
    /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).