From: Jeff King <peff@peff.net>
To: David Kastrup <dak@gnu.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Ping Yin <pkufranky@gmail.com>
Subject: Re: Addendum to "MaintNotes"
Date: Thu, 22 Nov 2007 06:09:11 -0500 [thread overview]
Message-ID: <20071122110910.GD10389@sigill.intra.peff.net> (raw)
In-Reply-To: <85pry2ftee.fsf@lola.goethe.zz>
On Thu, Nov 22, 2007 at 11:48:09AM +0100, David Kastrup wrote:
> > Now I've written this down, I can sleep well at night, knowing
> > that I can safely be hit by a bus any day ;-)
>
> So regarding git development, a bus error will no longer imply a core
> dump?
I'm slightly ashamed to admit to laughing at that.
-Peff
next prev parent reply other threads:[~2007-11-22 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 13:11 What is the whole process of cooking git as a maintainer? Ping Yin
2007-11-21 13:17 ` Ping Yin
2007-11-21 14:07 ` Theodore Tso
2007-11-21 14:45 ` Johannes Schindelin
2007-11-22 0:32 ` Addendum to "MaintNotes" Junio C Hamano
2007-11-22 10:36 ` Jeff King
2007-11-22 10:42 ` Junio C Hamano
2007-11-22 10:48 ` David Kastrup
2007-11-22 11:09 ` Jeff King [this message]
2007-11-22 11:08 ` Jeff King
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=20071122110910.GD10389@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pkufranky@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 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).