All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
	Johannes Sixt <J.Sixt@eudaptics.com>,
	git@vger.kernel.org
Subject: Re: MinGW binary installer available
Date: Thu, 8 Feb 2007 22:26:05 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0702082224380.22628@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <20070208212259.GA1091@spearce.org>

Hi,

On Thu, 8 Feb 2007, Shawn O. Pearce wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > Frankly, I'd rather stay away from such hackeries. For now, we can ship 
> > bash, perl and Tcl/Tk with Git, as well as git-gui, can't we? After all, 
> > Windows users are used to bloatware. Then, we just hide the command line 
> > from them!
> 
> I agree.
> 
> I'm happy to make changes in git-gui to help users who are trying
> to use Git without Cygwin, and are on Windows.  Patches would be
> even more welcome of course.  ;-)
> 
> Most of git-gui tries to stay away from shell scripts, partly for
> this reason, and partly because its Porcelain and shouldn't depend
> on the stock Porcelain-ish that comes with Git.  Oh, and shell
> scripts on Cygwin aren't speed-demons.  :-)

I was talking about MinGW. Shipping MSYS' bash, perl and tcltk would not 
be impossible. And configuring git-gui to be started with MSYS' wish would 
solve the common problems calling bash scripts.

Ciao,
Dscho

  reply	other threads:[~2007-02-08 21:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 14:38 MinGW binary installer available Han-Wen Nienhuys
2007-02-07 14:55 ` Johannes Schindelin
2007-02-07 15:05   ` Johannes Schindelin
2007-02-07 15:14     ` Han-Wen Nienhuys
2007-02-08  8:09     ` Johannes Sixt
2007-02-07 15:08   ` Han-Wen Nienhuys
2007-02-07 15:26     ` Johannes Schindelin
2007-02-07 15:34       ` Han-Wen Nienhuys
2007-02-07 16:16         ` Johannes Schindelin
2007-02-07 17:05           ` Han-Wen Nienhuys
2007-02-07 17:10             ` Johannes Schindelin
2007-02-07 17:35               ` Han-Wen Nienhuys
2007-02-07 21:10     ` Han-Wen Nienhuys
2007-02-08  8:12       ` Johannes Sixt
2007-02-08  8:09     ` Johannes Sixt
2007-02-08 10:14       ` Han-Wen Nienhuys
2007-02-08 21:15       ` Robin Rosenberg
2007-02-08 21:18         ` Johannes Schindelin
2007-02-08 21:22           ` Shawn O. Pearce
2007-02-08 21:26             ` Johannes Schindelin [this message]
2007-02-07 16:03   ` Han-Wen Nienhuys
2007-02-07 20:18     ` Jan Nieuwenhuizen
2007-02-07 21:21   ` Han-Wen Nienhuys
2007-02-07 23:51     ` Johannes Schindelin
2007-02-07 22:10   ` Han-Wen Nienhuys
2007-02-07 23:52     ` Johannes Schindelin
2007-02-08 19:58       ` Jan Nieuwenhuizen
2007-02-08 20:08         ` Johannes Schindelin

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.63.0702082224380.22628@wbgn013.biozentrum.uni-wuerzburg.de \
    --to=johannes.schindelin@gmx.de \
    --cc=J.Sixt@eudaptics.com \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    --cc=spearce@spearce.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 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.