All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@googlemail.com>
To: git@vger.kernel.org
Cc: msysgit@googlegroups.com, Erik Faye-Lund <kusmabite@gmail.com>
Subject: [PATCH v5 0/8] imap-send: Windows support
Date: Wed, 21 Oct 2009 19:04:43 +0200	[thread overview]
Message-ID: <1256144691-2908-1-git-send-email-kusmabite@gmail.com> (raw)


Here's the 5th iteration of my patches for
Windows-compatibility in imap-send.

 - Patch 1-3 is about getting rid of or rewriting
   code with portability issues.
 - Patch 4 fixes a compilation error on Windows
 - Patch 5 enables compilation of imap-send
 - Patch 6-7 enables SSL-suport for mingw
 - Patch 8 enables imap-send and SSL for msvc

The only change compared to the previous iteration
is that patch 7 and 8 enables NEEDS_CRYPTO_WITH_SSL.

Please note that I haven't tested Patch 8 with
NEEDS_CRYPTO_WITH_SSL under MSVC, as I don't have a
working setup with both msysgit and MSVC installed.

I'd love it if someone with such a working setup
could verify that it works, preferrably also with
BLK_SHA1 enabled.

Erik Faye-Lund (6):
  imap-send: use separate read and write fds
  imap-send: use run-command API for tunneling
  imap-send: fix compilation-error on Windows
  imap-send: build imap-send on Windows
  mingw: wrap SSL_set_(w|r)fd to call _get_osfhandle
  mingw: enable OpenSSL

Jeff King (1):
  imap-send: remove useless uid code

Marius Storm-Olsen (1):
  MSVC: Enable OpenSSL, and translate -lcrypto

 Makefile                        |    6 +-
 compat/mingw.h                  |   21 ++++
 compat/vcbuild/scripts/clink.pl |    3 +
 contrib/buildsystems/engine.pl  |    3 +
 imap-send.c                     |  226 +++++++++------------------------------
 5 files changed, 79 insertions(+), 180 deletions(-)

             reply	other threads:[~2009-10-21 17:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 17:04 Erik Faye-Lund [this message]
2009-10-21 17:04 ` [PATCH v5 1/8] imap-send: remove useless uid code Erik Faye-Lund
2009-10-21 17:04   ` [PATCH v5 2/8] imap-send: use separate read and write fds Erik Faye-Lund
2009-10-21 17:04     ` [PATCH v5 3/8] imap-send: use run-command API for tunneling Erik Faye-Lund
2009-10-21 17:04       ` [PATCH v5 4/8] imap-send: fix compilation-error on Windows Erik Faye-Lund
2009-10-21 17:04         ` [PATCH v5 5/8] imap-send: build imap-send " Erik Faye-Lund
2009-10-21 17:04           ` [PATCH v5 6/8] mingw: wrap SSL_set_(w|r)fd to call _get_osfhandle Erik Faye-Lund
2009-10-21 17:04             ` [PATCH v5 7/8] mingw: enable OpenSSL Erik Faye-Lund
2009-10-21 17:04               ` [PATCH v5 8/8] MSVC: Enable OpenSSL, and translate -lcrypto Erik Faye-Lund
2009-10-22 18:38               ` [msysGit] [PATCH v5 7/8] mingw: enable OpenSSL Johannes Sixt
2009-10-22 17:42 ` [msysGit] [PATCH v5 0/8] imap-send: Windows support Johannes Schindelin
2009-10-22 18:11   ` [msysGit] " Johannes Sixt
2009-10-22 18:26     ` [PATCH ef/msys-imap] mingw: use BLK_SHA1 again Johannes Sixt
2009-10-26 22:26       ` Johannes Schindelin
2009-10-27  6:56         ` Johannes Sixt
2009-10-22 19:20     ` [msysGit] Re: [PATCH v5 0/8] imap-send: Windows support Junio C Hamano

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=1256144691-2908-1-git-send-email-kusmabite@gmail.com \
    --to=kusmabite@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=kusmabite@gmail.com \
    --cc=msysgit@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.