From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: GIT on MinGW problem
Date: Sat, 26 May 2007 23:26:48 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705262318190.4648@racer.site> (raw)
In-Reply-To: <f3a2ke$9s7$1@sea.gmane.org>
Hi,
On Sat, 26 May 2007, Han-Wen Nienhuys wrote:
> Johannes Sixt escreveu:
> >>
> >> http://lilypond.org/git/binaries/mingw/git-1.5.1-2.mingw.exe
> >>
> >> it should also set $PATH.
> >
> > I gave this some more testing and it turns out to be a well working
> > toolset. Thank you very much!
> >
> > There were still some issues remaining. These are the ones that should
> > be fixable easily:
> >
> > * git version reports just:
> >
> > git version -dirty
> >
> > Since git-gui parses the output of git version, but does not expect it
> > to be of this format, and fails with an error message that it cannot
> > parse the version.
>
> My biggest problem is that the makefiles of git are an unmitigated
> disaster, and there seems to be little interest in solving this
> problem. For example, my suggestion to introduce autoconf was met with
> derision.
Well, I would not call it derision. But many people have had bad
experience with that big mess which is autoconf, so we were more than
reluctant to do it.
In the meantime, we do have a configure.ac, though. In general, you do not
have to run it, but you can if "make" does not work out of the box.
I have to admit that it is unclear to me what are the problems with the
Makefile with regards to gub. I think I will just bite the apple, and
download that beast to try it myself.
> In this, part of the pain is that Git tries to guess the version number
> by itself in a complicated way.
Yes, I never understood that myself why it has to be so complicated. But
then, it did not make _my_ life hard, so I did not care.
> I thought the policy was to abandon Perl scripts for git commands?
Alas, no. We even have picked up a few since.
OTOH, it _is_ a nice thing to protohype the new commands as shell or perl
scripts. When they stabilize enough, convert them to builtins.
There are exactly 4 perl scripts left that I regularly use:
add--interactive, cvsimport, remote and svn.
I somehow have the feeling that it is not worth the effort to convert
cvsimport and svn. With add--interactive, I think it's better to leave it
as is before Junio goes on another "what have I done? why did I have to
add _this_?" spree.
But remote will soon be the center of my crosshairs.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-26 22:27 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 1:13 GIT on MinGW problem Aaron Gray
2007-05-12 1:17 ` Junio C Hamano
2007-05-12 2:25 ` Aaron Gray
2007-05-12 3:30 ` Han-Wen Nienhuys
2007-05-25 8:49 ` Johannes Sixt
2007-05-25 9:45 ` Marco Costalba
2007-05-25 10:20 ` Johannes Schindelin
2007-05-25 11:07 ` Johannes Sixt
2007-05-26 19:42 ` Han-Wen Nienhuys
2007-05-26 22:17 ` Johannes Schindelin
2007-05-27 6:56 ` Han-Wen Nienhuys
2007-05-27 10:52 ` Johannes Schindelin
2007-05-27 17:04 ` Han-Wen Nienhuys
2007-05-28 16:54 ` Nix
2007-05-27 20:44 ` Han-Wen Nienhuys
[not found] ` <Pine.LNX.4.64.0705272213350.4648@racer.site>
[not found] ` <f329bf540705271417k1874c1f2u3acc98dc25e058b9@mail.gmail.com>
2007-05-27 21:26 ` Johannes Schindelin
2007-05-25 21:37 ` Aaron Gray
2007-05-26 19:41 ` Han-Wen Nienhuys
2007-05-26 22:26 ` Johannes Schindelin [this message]
2007-05-26 22:39 ` Junio C Hamano
2007-05-26 22:45 ` Johannes Schindelin
2007-05-26 22:53 ` Han-Wen Nienhuys
2007-05-26 23:47 ` Jakub Narebski
2007-05-27 6:30 ` Han-Wen Nienhuys
2007-05-27 6:39 ` Shawn O. Pearce
2007-05-27 7:02 ` Han-Wen Nienhuys
2007-05-27 7:21 ` Steven Grimm
2007-05-27 9:09 ` Jakub Narebski
2007-05-27 23:18 ` Han-Wen Nienhuys
2007-05-28 0:04 ` Johannes Schindelin
2007-05-28 0:31 ` Han-Wen Nienhuys
2007-05-27 10:46 ` Johannes Schindelin
2007-05-27 18:50 ` Han-Wen Nienhuys
2007-05-27 19:52 ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-27 20:39 ` Aaron Gray
2007-05-27 21:19 ` Han-Wen Nienhuys
2007-05-27 21:24 ` Aaron Gray
2007-05-27 21:39 ` Aaron Gray
2007-05-27 21:55 ` Han-Wen Nienhuys
2007-05-27 22:22 ` Aaron Gray
2007-05-27 22:28 ` Han-Wen Nienhuys
2007-05-27 22:56 ` GIT on MinGW - No symbolic links support Aaron Gray
2007-05-27 23:56 ` Johannes Schindelin
2007-05-29 7:11 ` Johannes Sixt
2007-05-27 22:22 ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-29 10:54 ` GIT on MinGW problem Johannes Sixt
2007-05-29 11:45 ` Marius Storm-Olsen
2007-05-29 12:10 ` Johannes Sixt
2007-05-29 14:29 ` Han-Wen Nienhuys
2007-05-29 14:49 ` Johannes Sixt
2007-05-29 12:11 ` Johannes Schindelin
2007-05-29 13:05 ` Marius Storm-Olsen
2007-05-29 13:24 ` Johannes Sixt
2007-05-29 14:36 ` Marius Storm-Olsen
2007-05-29 13:47 ` Johannes Schindelin
2007-05-29 14:13 ` Johannes Sixt
2007-05-29 15:28 ` Nguyen Thai Ngoc Duy
2007-05-29 15:47 ` Johannes Sixt
2007-05-29 18:45 ` Nguyen Thai Ngoc Duy
2007-05-30 3:03 ` [PATCH] Make git-k an alias to gitk Johannes Schindelin
2007-05-30 7:06 ` Johannes Sixt
2007-05-30 2:16 ` GIT on MinGW problem Han-Wen Nienhuys
2007-05-30 2:39 ` Johannes Schindelin
2007-05-30 2:57 ` Shawn O. Pearce
2007-05-30 3:25 ` [PATCH] Git wrapper: add --redirect-stderr option Johannes Schindelin
2007-05-30 3:38 ` Shawn O. Pearce
2007-05-30 3:45 ` Johannes Schindelin
2007-05-30 3:53 ` Shawn O. Pearce
2007-05-30 4:12 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-05-12 14:20 GIT on MinGW problem Aaron Gray
[not found] ` <033501c79710$a2eb0290$0200a8c0@AMD2500>
2007-05-15 19:51 ` Han-Wen Nienhuys
2007-05-16 8:02 ` Johannes Sixt
2007-05-21 18:22 ` Nguyen Thai Ngoc Duy
2007-05-26 23:08 ` Han-Wen Nienhuys
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.0705262318190.4648@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).