From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Jason Riedy <ejr@EECS.Berkeley.EDU>, git <git@vger.kernel.org>
Subject: Re: [PATCH] Add a compat/strtoumax.c for Solaris 8.
Date: Mon, 19 Feb 2007 21:51:10 -0500 [thread overview]
Message-ID: <20070220025110.GA28797@spearce.org> (raw)
In-Reply-To: <7vfy9136zu.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Yours talk about Sol 9 and Jason talks about Sol 8. Should I
> take your ack to mean you want this patch on top of Jason's?
Yes, indeed. Please apply that. :-)
--
Shawn.
next prev parent reply other threads:[~2007-02-20 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 0:22 [PATCH] Add a compat/strtoumax.c for Solaris 8 Jason Riedy
2007-02-20 0:35 ` Shawn O. Pearce
2007-02-20 0:53 ` Junio C Hamano
2007-02-20 0:58 ` Shawn O. Pearce
2007-02-20 1:29 ` Junio C Hamano
2007-02-20 2:20 ` Junio C Hamano
2007-02-20 2:51 ` Shawn O. Pearce [this message]
2007-02-20 3:00 ` Junio C Hamano
2007-02-20 20:16 ` Jason Riedy
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=20070220025110.GA28797@spearce.org \
--to=spearce@spearce.org \
--cc=ejr@EECS.Berkeley.EDU \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).