git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: MinGW binary installer available
Date: Wed, 07 Feb 2007 16:14:06 +0100	[thread overview]
Message-ID: <45C9ECBE.6010705@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.63.0702071559340.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin escreveu:
> Hi,
> 
> On Wed, 7 Feb 2007, Johannes Schindelin wrote:
> 
>> On Wed, 7 Feb 2007, Han-Wen Nienhuys wrote:
>>
>>> I don't actually have a windows copy, so it's basically untested.
>>> However, I did succeed in running rev-list in wine.
>> I played a little with it. IMHO it makes no sense to use it without a 
>> bash, and without less.
> 
> Side note: Since "ln <src> <dest>" in MinGW is really a copy, not a hard 
> link, this gets rather big (44M here).
> 
> Which makes me think if we should just disallow the "git-<builtin>" on 
> Windows, since sooner or later, Git will no longer be used from the 
> command line on Windows.
> 
> And another thing hit me there: Are you sure that all works well if you 
> change the install path from "C:\Program Files\Git" to something else?
> Without explicitely setting GIT_EXEC_PATH?

I have no idea. The installer just plonks the files into C:/P F/Git/
and adds that to $INSTALLDIR/usr/bin/ to $PATH


-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

  reply	other threads:[~2007-02-07 15:14 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 [this message]
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
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=45C9ECBE.6010705@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=janneke@gnu.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).