From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: "Duy Nguyen" <pclouds@gmail•com>,
"Stefan Näwe" <stefan.naewe@atlas-elektronik•com>,
Armin <netzverweigerer@gmail•com>, "Jonathon Mah" <jmah@me•com>,
"git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: segmentation fault (nullpointer) with git log --submodule -p
Date: Thu, 24 Jan 2013 20:21:32 -0800 [thread overview]
Message-ID: <7vmwvx7v03.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130125040856.GA30533@sigill.intra.peff.net> (Jeff King's message of "Thu, 24 Jan 2013 23:08:56 -0500")
Jeff King <peff@peff•net> writes:
> ... I know it gets the job done, but in my
> experience, macros which do not behave syntactically like functions are
> usually a good sign that you are doing something gross and
> unmaintainable.
Yeah, it is a bit too cute for my taste, too, even though it was fun
;-)
next prev parent reply other threads:[~2013-01-25 4:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 14:38 segmentation fault (nullpointer) with git log --submodule -p Armin
2013-01-23 20:02 ` Jeff King
2013-01-24 12:11 ` Stefan Näwe
2013-01-24 13:40 ` Duy Nguyen
2013-01-24 14:06 ` Stefan Näwe
2013-01-24 14:14 ` Duy Nguyen
2013-01-24 23:27 ` Jeff King
2013-01-24 23:56 ` Junio C Hamano
2013-01-25 0:55 ` Jeff King
2013-01-25 2:05 ` Duy Nguyen
2013-01-25 3:59 ` Junio C Hamano
2013-01-25 4:08 ` Jeff King
2013-01-25 4:21 ` Junio C Hamano [this message]
2013-01-25 5:53 ` Jonathan Nieder
2013-01-25 7:27 ` Junio C Hamano
2013-01-25 7:32 ` Jonathon Mah
2013-01-25 15:36 ` Junio C Hamano
2013-01-26 9:40 ` [PATCH 0/3] lazily load commit->buffer Jeff King
2013-01-26 9:42 ` [PATCH 1/3] commit: drop useless xstrdup of commit message Jeff King
2013-01-26 9:44 ` [PATCH 2/3] logmsg_reencode: never return NULL Jeff King
2013-01-26 9:44 ` [PATCH 3/3] logmsg_reencode: lazily load missing commit buffers Jeff King
2013-01-26 21:26 ` [PATCH 0/3] lazily load commit->buffer Junio C Hamano
2013-01-26 22:14 ` Jeff King
2013-01-27 5:32 ` Junio C Hamano
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=7vmwvx7v03.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jmah@me$(echo .)com \
--cc=netzverweigerer@gmail$(echo .)com \
--cc=pclouds@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=stefan.naewe@atlas-elektronik$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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