All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: [patch] fix imap-send for OSX
Date: Wed, 15 Mar 2006 15:50:17 -0800	[thread overview]
Message-ID: <7v8xrbfeti.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86slpj5ljp.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "15 Mar 2006 15:35:06 -0800")

Thanks.

How much would we care about non GNU libc I wonder.  We could
just lose that private definition, and say 

	#define _GNU_SOURCE
        #include <stdio.h>

instead, in git-compat-util.h.

But let's leave that to later rounds.

      reply	other threads:[~2006-03-15 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 22:13 What's in git.git Junio C Hamano
2006-03-15 23:35 ` [patch] fix imap-send for OSX Randal L. Schwartz
2006-03-15 23:50   ` Junio C Hamano [this message]

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=7v8xrbfeti.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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.