From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: git@vger.kernel.org, Johannes Sixt <J.Sixt@eudaptics.com>,
Han-Wen Nienhuys <hanwen@xs4all.nl>
Subject: [PATCH] Mention libiconv as a requirement for git-am
Date: Tue, 31 Jul 2007 11:09:48 -0400 [thread overview]
Message-ID: <20070731150948.GA9947@localhost> (raw)
---
Han-Wen, any chance to include libiconv to the installer? You may need
to set NEEDS_ICONV, ICONVDIR and NO_ICONV properly to make git-am work.
README.MinGW | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/README.MinGW b/README.MinGW
index 89b7065..c0b8f66 100644
--- a/README.MinGW
+++ b/README.MinGW
@@ -28,6 +28,7 @@ In order to compile this code you need:
zlib-1.2.3-mingwPORT-1.tar
w32api-3.6.tar.gz
tcltk-8.4.1-1.exe (for gitk, git-gui)
+ libiconv-1.9.2-1-{lib,bin}.zip (for git-am, from http://gnuwin32.sourceforge.net/packages/libiconv.htm)
STATUS
--
1.5.0.7
next reply other threads:[~2007-07-31 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 15:09 Nguyen Thai Ngoc Duy [this message]
2007-08-01 3:03 ` [PATCH] Mention libiconv as a requirement for git-am Han-Wen Nienhuys
2007-08-01 3:18 ` Nguyen Thai Ngoc Duy
2007-08-01 3:36 ` 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=20070731150948.GA9947@localhost \
--to=pclouds@gmail.com \
--cc=J.Sixt@eudaptics.com \
--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).