From: Steffen Prohaska <prohaska@zib.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Johannes Sixt <johannes.sixt@telecom.at>
Subject: [PATCH 0/3] git-gui (Windows): Adapt to new execdir 'libexec/git-core'
Date: Sun, 27 Jul 2008 18:49:40 +0200 [thread overview]
Message-ID: <1217177383-25272-1-git-send-email-prohaska@zib.de> (raw)
After moving the dashed programs, including git-gui, to execdir
'libexec/git-core', we have problems running git-gui from
msysgit.
The following patch series solves the problems. I am not sure
however if it is the less intrusive solution. Maybe the series
needs further discussion before applying it. Personally, I think
the patches are good enough.
Note that you also need the branch 'spr/installer' in msysgit to
build an installer.
[PATCH 1/3] git-gui: Adapt discovery of oguilib to execdir 'libexec/git-core'
[PATCH 2/3] git-gui (Windows): Switch to relative discovery of oguilib
[PATCH 3/3] git-gui (Windows): Change wrapper to execdir 'libexec/git-core'
next reply other threads:[~2008-07-27 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 16:49 Steffen Prohaska [this message]
2008-07-27 16:49 ` [PATCH 1/3] git-gui: Adapt discovery of oguilib to execdir 'libexec/git-core' Steffen Prohaska
2008-07-27 16:49 ` [PATCH 2/3] git-gui (Windows): Switch to relative discovery of oguilib Steffen Prohaska
2008-07-27 16:49 ` [PATCH 3/3] git-gui (Windows): Change wrapper to execdir 'libexec/git-core' Steffen Prohaska
2008-07-27 21:24 ` [PATCH 1/3] git-gui: Adapt discovery of oguilib " Shawn O. Pearce
2008-07-28 5:01 ` Steffen Prohaska
2008-07-30 5:25 ` Shawn O. Pearce
2008-07-30 5:39 ` Steffen Prohaska
2008-08-03 9:35 ` Johannes Sixt
2008-08-03 10:09 ` Steffen Prohaska
2008-08-04 19:58 ` [PATCH] " Johannes Sixt
2008-08-04 20:00 ` Shawn O. Pearce
2008-08-04 20:09 ` [PATCH v2] " Johannes Sixt
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=1217177383-25272-1-git-send-email-prohaska@zib.de \
--to=prohaska@zib.de \
--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).