From: "Shawn O. Pearce" <spearce@spearce.org>
To: Imre Deak <imre.deak@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] builtin-apply: fix typo leading to stack corruption
Date: Thu, 9 Oct 2008 09:04:28 -0700 [thread overview]
Message-ID: <20081009160428.GB29829@spearce.org> (raw)
In-Reply-To: <7v4p3mors6.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> Looks good and would look better with a sign-off.
I'm holding off on applying this change for a little, hoping Imre
can give us a sign off, but really I don't think anyone can claim
copyright to the < sign. If they can, we're in big trouble. :-)
--
Shawn.
next prev parent reply other threads:[~2008-10-09 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 21:24 [PATCH] builtin-apply: fix typo leading to stack corruption Imre Deak
2008-10-09 12:51 ` Junio C Hamano
2008-10-09 16:04 ` Shawn O. Pearce [this message]
2008-10-09 16:07 ` Brandon Casey
2008-10-09 16:12 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2008-10-08 21:24 Imre Deak
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=20081009160428.GB29829@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=imre.deak@gmail.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.