git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: msysGit and SCons: broken?
Date: Thu, 06 Aug 2009 21:45:46 +0200	[thread overview]
Message-ID: <4A7B32EA.2080505@dirk.my1.cc> (raw)
In-Reply-To: <alpine.DEB.1.00.0908040010220.8306@pacific.mpi-cbg.de>

Am 04.08.2009 00:13 schrieb Johannes Schindelin:
> On Mon, 3 Aug 2009, Dirk Süsserott wrote:
> 
> I suspect the appropriate mailing list would have been the msysGit list, 
> then.

Sorry, next time I'll have a look there, but I'm more familiar with this 
list. :-)

> How does your SCons call relate to Git?  Do you call it from the Git Bash?  
> Do you call it from cmd.exe directly?  Is Git/bash in your PATH?

My SCons call doesn't actually relate to Git. I just use the Git-bash as 
my favorite shell under Windows. It's by far better than the regular 
cmd.exe. Despite I'm using Windows, I'm a "shell person" and prefer not 
to use only my index finger to direct the computer :-). Git-bash gives 
that opportunity.

I used to call SCons from Git-bash and it worked. After Git's upgrade 
(or some other unknown change) I did the same and it didn't work from 
Git-bash, but it still worked from cmd.exe. Git-bash ist not in my PATH 
when I run cmd.exe.

Don't bother, I just posed the question and hoped someone says "yeah, I 
faced the same problem and solved it like this: ...". I'll use a 
workaround and post a solution if I find one.

     Dirk

  reply	other threads:[~2009-08-06 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 18:19 msysGit and SCons: broken? Dirk Süsserott
2009-08-03 22:13 ` Johannes Schindelin
2009-08-06 19:45   ` Dirk Süsserott [this message]
2009-08-13 19:32     ` Dirk Süsserott
2009-08-13 21:54       ` Johannes Schindelin
2009-08-15 14:04         ` Dirk Süsserott

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=4A7B32EA.2080505@dirk.my1.cc \
    --to=newsletter@dirk.my1.cc \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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).