All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: <randall.s.becker@rogers.com>, <git@vger.kernel.org>
Subject: Re: [PATCH v4 3/4] Bring NonStop platform definitions up to date in git-compat-util.h
Date: Wed, 24 Jan 2018 13:45:25 -0800	[thread overview]
Message-ID: <xmqqefmfaq2y.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqzi53arda.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 24 Jan 2018 13:17:37 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> "Randall S. Becker" <rsbecker@nexbridge.com> writes:
>
>>> > +#ifdef __TANDEM
>>> > +#if !defined(_THREAD_SUPPORT_FUNCTIONS) &&
>>> !defined(_PUT_MODEL_)
>>> > +/* #include <floss.h(floss_read,floss_write,floss_fsync,floss_fork)>
>>> > +*/
>>> > +/* #include <floss.h(floss_fork)> */
>>> > +#endif
>>> 
>>> The above adds a conditional no-op?  That's confusing...
>>
>> We are trying to make PUT work with git on NonStop. I can't tell you how
>> much of a pain it is. This is a placeholder for others (outside our group)
>> to know where to muck. I can remove it if you don't want it there.
>
> It is OK as long as it was done on purpose.  I was just making sure
> that this was an unfinished WIP sent by mistake before proofreading.

Obviously, I was trying to make sure it was *NOT* an incomplete
state you did not intend to send ;-)


  reply	other threads:[~2018-01-24 21:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 23:41 [PATCH v4 0/4] Force pipes to flush immediately on NonStop platform randall.s.becker
2018-01-21 23:42 ` [PATCH v4 1/4] Add tar extract install options override in installation processing randall.s.becker
2018-01-24 20:33   ` Junio C Hamano
2018-01-24 22:01     ` Todd Zullinger
2018-01-24 22:27       ` Randall S. Becker
2018-01-24 23:39     ` Ramsay Jones
2018-01-21 23:42 ` [PATCH v4 2/4] Define config options required for the HPE NonStop NSX and NSE platforms randall.s.becker
2018-01-24 21:19   ` Junio C Hamano
2018-01-24 21:49     ` randall.s.becker
2018-01-21 23:42 ` [PATCH v4 3/4] Bring NonStop platform definitions up to date in git-compat-util.h randall.s.becker
2018-01-24 20:36   ` Junio C Hamano
2018-01-24 20:49     ` Randall S. Becker
2018-01-24 21:17       ` Junio C Hamano
2018-01-24 21:45         ` Junio C Hamano [this message]
2018-01-24 21:51         ` Randall S. Becker
2018-01-21 23:42 ` [PATCH v4 4/4] Add intptr_t and uintptr_t to regcomp.c for NonStop platform randall.s.becker

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=xmqqefmfaq2y.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=randall.s.becker@rogers.com \
    --cc=rsbecker@nexbridge.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.