From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Shawn Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: t8001-annotate.sh fails on Mac OS X
Date: Fri, 26 May 2006 15:12:09 +1200 [thread overview]
Message-ID: <46a038f90605252012u6aa97092w548d2b70b955f3dd@mail.gmail.com> (raw)
In-Reply-To: <7vpsi1qyi2.fsf@assigned-by-dhcp.cox.net>
On 5/26/06, Junio C Hamano <junkio@cox.net> wrote:
> Or git is not yet used in the real world.
Bah. Real world? Been there, not worth it...
m
next prev parent reply other threads:[~2006-05-26 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 23:53 t8001-annotate.sh fails on Mac OS X Stefan Pfetzing
2006-05-26 1:11 ` Shawn Pearce
2006-05-26 3:02 ` Junio C Hamano
2006-05-26 3:12 ` Martin Langhoff [this message]
2006-05-27 1:40 ` Ryan Anderson
2006-05-26 4:32 ` Fredrik Kuivinen
2006-05-26 13:36 ` Johannes Schindelin
2006-05-26 13:51 ` Stefan Pfetzing
2006-05-27 18:13 ` Nicolas Vilz 'niv'
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=46a038f90605252012u6aa97092w548d2b70b955f3dd@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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).