From: Junio C Hamano <junkio@cox.net>
To: John Ellson <ellson@research.att.com>
Cc: git@vger.kernel.org
Subject: Re: Status of Mac OS/X ports of git and cogito?
Date: Fri, 26 Aug 2005 20:50:08 -0700 [thread overview]
Message-ID: <7vd5o03uof.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <deofnh$jl0$1@sea.gmane.org> (John Ellson's message of "Fri, 26 Aug 2005 21:30:23 -0400")
John Ellson <ellson@research.att.com> writes:
> Do git and cogito build easily on Mac OS/X now? Are there
> binaries available anywhere?
Not that I know of. We used to get portability patches from
Darwin folks, but I haven't seen any lately.
I am somewhat interested in what portability glitches we still
have, but not having an access to a machine, it is more of a
curiosity rather than a necessity for me.
Are Darwin folks on the list happy with the current codebase, or
have you given up because it is too GNU/Linux specific?
next prev parent reply other threads:[~2005-08-27 3:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 1:30 Status of Mac OS/X ports of git and cogito? John Ellson
2005-08-27 3:50 ` Junio C Hamano [this message]
2005-09-11 10:07 ` Johannes Schindelin
2005-09-11 11:07 ` Martin Langhoff
2005-09-11 23:12 ` Johannes Schindelin
2005-09-11 17:34 ` Junio C Hamano
2005-09-11 17:46 ` Linus Torvalds
2005-09-11 18:16 ` A Large Angry SCM
2005-09-11 20:53 ` Junio C Hamano
2005-09-11 23:18 ` Johannes Schindelin
2005-09-11 18:07 ` Linus Torvalds
2005-09-11 21:01 ` [PATCH] Use int instead of socklen_t Junio C Hamano
2005-09-11 23:22 ` Status of Mac OS/X ports of git and cogito? Johannes Schindelin
2005-09-11 23:40 ` Linus Torvalds
2005-09-11 23:43 ` Linus Torvalds
2005-09-12 0:21 ` Johannes Schindelin
2005-09-11 18:43 ` Daniel Barkalow
2005-09-11 21:06 ` Martin Langhoff
2005-09-11 23:27 ` Johannes Schindelin
2005-08-27 6:59 ` Martin Langhoff
2005-08-29 7:16 ` Martin Langhoff
2005-08-30 10:04 ` Martin Langhoff
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=7vd5o03uof.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ellson@research.att.com \
--cc=git@vger.kernel.org \
/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).