git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: [PATCH 0/4]  misc. MSVC patches
Date: Wed, 23 Jun 2010 20:36:17 +0100	[thread overview]
Message-ID: <4C226231.40102@ramsay1.demon.co.uk> (raw)

Hi Junio,

I have been spring cleaning my branches and found these MSVC patches
down the back of the sofa. ;-)

Nothing very exciting, but I thought I would pass them on anyway.

The second patch may improve SHA1 performance slightly, but I have
not timed it.

I think some variant of the final patch has been seen on the list
before and was not applied; I don't remember much discussion, so
I don't recall if or why it was rejected...

Ramsay Jones (4):
  msvc: Fix some "expr evaluates to function" compiler warnings
  msvc: Select the "fast" definition of the {get,put}_be32() macros
  msvc: Fix some compiler warnings
  Makefile: Don't pass $(ALL_CFLAGS) to the linker

 Makefile          |   14 +++++++-------
 block-sha1/sha1.c |    9 +++++----
 builtin.h         |    4 ++--
 builtin/notes.c   |    2 +-
 notes.h           |    4 ++--
 5 files changed, 17 insertions(+), 16 deletions(-)


ATB,
Ramsay Jones

             reply	other threads:[~2010-06-23 19:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 19:36 Ramsay Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-20 19:19 [PATCH 0/4] misc. msvc patches Ramsay Jones
2010-01-20 20:57 ` Junio C Hamano
2010-01-22 19:28   ` Ramsay Jones

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=4C226231.40102@ramsay1.demon.co.uk \
    --to=ramsay@ramsay1.demon.co.uk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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).