git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christian MICHON" <christian.michon@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Johannes Sixt" <johannes.sixt@telecom.at>, git@vger.kernel.org
Subject: Re: MinGW port usable
Date: Tue, 30 Jan 2007 09:07:15 +0100	[thread overview]
Message-ID: <46d6db660701300007v573832b5pc7ac41059dc4490e@mail.gmail.com> (raw)
In-Reply-To: <46d6db660701292359v7647306fla30c9a10e5989dcc@mail.gmail.com>

On 1/30/07, Christian MICHON <christian.michon@gmail.com> wrote:
> On 1/30/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> > Try creating a desktop icon (Repository->Create Desktop Icon) and
> > start git-gui from the resulting .bat file.  It *should* come up
> > right on MinGW, but I'm only guessing here.
>
> ok, yes it's working. :)
> but call gitk from inside it fail :(
>
> "error in startup script"
> ( git-peek-remote is not working from git-gui, could be path related.
> It's hard to tell why yet)
>
> --
> Christian
>

just to be more clear: when using the .bat shortcut, calling gitk
from within git-gui fails.

But if I call git-gui from a msys rxvt+bash, I can invoke all tools,
and calling gitk from within git-gui works.

I think this shortcut stuff may not be the best approach yet.

-- 
Christian

  reply	other threads:[~2007-01-30  8:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 22:20 MinGW port usable Johannes Sixt
2007-01-29 22:35 ` Shawn O. Pearce
2007-01-29 23:11   ` Christian MICHON
2007-01-29 23:24     ` Shawn O. Pearce
2007-01-29 23:48       ` Christian MICHON
2007-01-30  7:59       ` Christian MICHON
2007-01-30  8:07         ` Christian MICHON [this message]
2007-01-30 10:16           ` Johannes Schindelin
2007-01-30 15:27             ` Shawn O. Pearce
2007-01-30 16:31           ` Johannes Sixt
2007-01-30  8:47   ` Johannes Sixt
2007-01-29 22:46 ` Linus Torvalds
2007-01-29 23:08   ` Christian MICHON
2007-01-30 10:08     ` Johannes Schindelin
2007-01-30 10:14       ` Christian MICHON
2007-01-30  8:45   ` Johannes Sixt
2007-01-30 14:35   ` Johannes Schindelin
2007-01-30 15:18     ` Shawn O. Pearce
2007-01-30 15:38       ` Johannes Schindelin
2007-01-30 15:56         ` Shawn O. Pearce
2007-01-30 16:12           ` Johannes Schindelin
2007-01-30 16:28             ` Shawn O. Pearce
2007-01-30 16:49               ` Johannes Schindelin
2007-01-30  0:50 ` Daniel Barkalow
2007-01-30  8:23   ` Johannes Sixt
2007-01-30  8:41     ` Andreas Ericsson
2007-01-30 10:07     ` Johannes Schindelin
2007-01-30 17:09     ` Daniel Barkalow
2007-01-30 17:36       ` Johannes Schindelin
2007-01-30 18:09         ` Daniel Barkalow
2007-01-30 20:20           ` Johannes Sixt
2007-01-30  5:53 ` Junio C Hamano
2007-02-01  6:35 ` H. Peter Anvin
2007-02-01 10:34   ` Johannes Sixt
2007-02-01 21:05     ` H. Peter Anvin
2007-02-02  8:28       ` H. Peter Anvin
2007-02-02  8:49         ` Davide Libenzi
2007-02-02  8:55         ` Johannes Sixt
2007-02-02  8:55         ` H. Peter Anvin

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=46d6db660701300007v573832b5pc7ac41059dc4490e@mail.gmail.com \
    --to=christian.michon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.sixt@telecom.at \
    --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 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).