From: "Daniel Richard G." <skunk@iSKUNK.ORG>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Building Git on Tru64
Date: Thu, 15 Apr 2010 15:46:49 -0400 [thread overview]
Message-ID: <1271360809.25304.1370186353@webmail.messagingengine.com> (raw)
In-Reply-To: <r2n81b0412b1004151229g6fe840a1v23a9d06f72e8d36a@mail.gmail.com>
On Thu, 2010 Apr 15 21:29+0200, Alex Riesen wrote:
>
> That one may be better handled at one place (git-compat-util.h?) with
> something like:
>
> #ifdef Tru64
> #define MAP_FAILED ((void *)MAP_FAILED)
> #endif
I agree with the sentiment, but you can't have a macro refer to itself
:]
> P.S. You may consider reading Documentation/SubmittingPatches. The way
> you did it is a little unconventional.
The patch isn't meant to be committed as-is, at least not all of it.
Some of these things need to be massaged in a little (e.g. having
hstrerror.c #include git-compat-util.h instead of just sticking #define
_OSF_SOURCE at the top), but I need to hear from others on how to go
about this.
--Daniel
(Please Cc: any replies to me, as I am not subscribed to this list.)
--
NAME = Daniel Richard G. _\|/_ Remember, skunks
MAIL = skunk@iSKUNK.ORG (/o|o\) _- don't smell bad---
MAIL+= skunk@alum.MIT.EDU < (^),> it's the people who
WWW = (not there yet!) / \ annoy us that do!
next prev parent reply other threads:[~2010-04-15 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 19:09 [PATCH] Building Git on Tru64 Daniel Richard G.
2010-04-15 19:29 ` Alex Riesen
2010-04-15 19:46 ` Daniel Richard G. [this message]
2010-04-15 20:04 ` Nicolas Pitre
2010-04-15 20:21 ` Daniel Richard G.
2010-04-15 21:24 ` Jakub Narebski
2010-04-16 6:58 ` Erik Faye-Lund
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=1271360809.25304.1370186353@webmail.messagingengine.com \
--to=skunk@iskunk.org \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.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.