From: Josh Triplett <josh@freedesktop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jim Meyering <jim@meyering.net>, Geert Bosch <bosch@adacore.com>,
Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] git-log: detect dup and fdopen failure
Date: Wed, 27 Jun 2007 19:46:54 -0700 [thread overview]
Message-ID: <4683211E.2010704@freedesktop.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0706270935340.8675@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
Linus Torvalds wrote:
> On Wed, 27 Jun 2007, Jim Meyering wrote:
>> Subject: [PATCH] git-log: detect dup and fdopen failure
>> git-compat-util.h (xdup, xfdopen): Define functions.
>>
>> Signed-off-by: Jim Meyering <jim@meyering.net>
>
> Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
>
> That said, the whole "prepend 'x' to the function name" thing is obviously
> how git does things, but maybe it would be more readable in the long term
> to make the prefix be 'safe_' instead of 'x', or something like that?
If you want a more verbose name than xfoo, I personally like the foo_or_die
convention, which reminds you explicitly that the function might kill the
program. safe_ might convey exactly the opposite impression.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-06-28 2:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 11:59 [PATCH] detect dup failure Jim Meyering
2007-06-27 12:48 ` Alex Riesen
2007-06-27 13:02 ` [PATCH] git-log: detect dup and fdopen failure Jim Meyering
2007-06-27 13:18 ` Alex Riesen
2007-06-27 13:32 ` Jim Meyering
2007-06-27 14:04 ` Alex Riesen
2007-06-27 14:14 ` Jim Meyering
2007-06-27 15:57 ` Alex Riesen
2007-06-27 16:34 ` Jim Meyering
2007-06-27 13:54 ` Geert Bosch
2007-06-27 14:06 ` Jim Meyering
2007-06-27 14:28 ` Jim Meyering
2007-06-27 16:49 ` Linus Torvalds
2007-06-28 2:46 ` Josh Triplett [this message]
2007-06-28 5:02 ` Shawn O. Pearce
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=4683211E.2010704@freedesktop.org \
--to=josh@freedesktop.org \
--cc=bosch@adacore.com \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
--cc=raa.lkml@gmail.com \
--cc=torvalds@linux-foundation.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).